[Java] Tool-as-lambda 4.6: Update Java docs and ADR cross-links

[edburns]

Important

You MUST branch from upstream/edburns/1810-java-tool-ergonomics-tool-as-lambda

Do NOT use main as your base branch. The plan files and context referenced below exist ONLY on upstream/edburns/1810-java-tool-ergonomics-tool-as-lambda.

• Create your topic branch from: upstream/edburns/1810-java-tool-ergonomics-tool-as-lambda
• Your PR must target: upstream/edburns/1810-java-tool-ergonomics-tool-as-lambda
• The first line of your PR description must be: Fixes #1884

---

Overview

Implement Phase 4.6 of #1810: update Java documentation for inline lambda-defined tools and ensure ADR linkage is clear.

Before coding

• Do not start any implementation work until this issue is explicitly assigned to the coding agent.
• Base branch for this work:
  edburns/1810-java-tool-ergonomics-tool-as-lambda.
• Read this plan file on the branch before coding:
  1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md

Ordering rule (important)

This issue starts only after 4.5 is merged; all Phase 4 issues are completed in listed order.

Relevant Phase 3 resolutions to apply

• 3.1 / 3.2: document the final API families and usage style.
• 3.3: document Param<T> usage and required/default behavior.
• 3.6: document fluent option modifiers on ToolDefinition.
• 3.8: keep user-facing docs aligned with final package placement and exported API.

Scope / deliverables

1. Update java/README.md with concise, accurate examples of inline lambda tool definitions.
2. Update java/docs/adr/adr-006-tool-definition-inline.md only where clarifications are needed to reflect final API names/usage.
3. Ensure examples are consistent with implemented API and behavior.

Gating criteria

• Documentation reflects final API accurately and is internally consistent.
• README includes at least one concise inline tool example.

Constraints

IMPORTANT: you must run mvn spotless:apply in the java directory before every commit.

• Keep changes focused to Java docs directly related to this feature.
• Follow repository docs style guidance.

Completion bookkeeping

When complete, update the checkbox for Phase 4.6 in:
1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md

[copilot-swe-agent]

The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: 1D74:1BABD5:209404:7359AC:6A45B555)

[copilot-swe-agent]

The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: 0CC3:281C0B:1164BD:3CF9F4:6A45B5A4)

[github-actions]

Documentation Gap Analysis

This issue (Phase 4.6 of #1810) identifies the following documentation gaps for the Java inline lambda-defined tools feature:

What is missing or needs updating

1. java/README.md

• Missing concise, accurate examples of defining tools as inline lambdas using the new API
• Should include at least one end-to-end inline tool definition example showing the final API

2. java/docs/adr/adr-006-tool-definition-inline.md

• Needs clarifications to reflect final API names and usage patterns (where they differ from the ADR's original design)

Specific content gaps (from Phase 3 resolutions)

Phase 3 Resolution	What to Document
3.1 / 3.2	Final API families and usage style for inline lambda tools
3.3	Param usage: required fields and default behavior
3.6	Fluent option modifiers on ToolDefinition
3.8	Correct package placement and exported API surface

Gating criteria

• README includes at least one concise inline lambda tool example
• All examples are consistent with the implemented API on branch edburns/1810-java-tool-ergonomics-tool-as-lambda
• ADR cross-links are accurate and reflect the final implementation

Note: Implementation work on this branch should follow the plan file at 1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md and only begin once Phase 4.5 is merged.

Generated by Documentation Handler for issue #1884 · sonnet46 442.9K · ◷

[edburns]

@copilot IMPORTANT: You MUST create your branch from upstream/edburns/1810-java-tool-ergonomics-tool-as-lambda and target your PR at upstream/edburns/1810-java-tool-ergonomics-tool-as-lambda. Do NOT use main. The plan files referenced in this issue only exist on upstream/edburns/1810-java-tool-ergonomics-tool-as-lambda.