daierenao opened a new pull request, #1261: URL: https://github.com/apache/flink-agents/pull/1261
Closes #1250 ### Purpose of change The Tool Use guide mixes user-facing configuration with internal scheduling details and leaves parameter-injection behavior spread across pages. Clarify tool declaration and registration, injection sources and override/failure rules, and parallel-call configuration, independence requirements, and timeout boundaries. Correct incomplete declaration snippets and link the YAML, chat, and configuration references to the relevant sections. Use the implemented `async.batch.parallelism` option rather than the `tool-call.parallelism` name mentioned in the issue. Existing section anchors and the old Tool Use URL alias are preserved. No runtime behavior or configuration defaults change. ### Tests - Hugo extended 0.110.0 documentation build; checked 348 internal links/anchors across the four changed generated pages, the old Tool Use alias, and the example source links. - All eight Python fenced examples parse. Minimal Java/Python API wrappers validate configuration, tool/resource declaration, and ReActAgent construction. - Clean Java reactor rebuild and focused `ToolCallActionTest` / `FunctionToolTest` suites: 30 passed. Python tool-action, function-tool, and decorator suites: 89 passed, importing the current checkout. - `git diff --check` passed. Java validation uses JDK 26 with the Java 11 compilation target. No real Flink job, external model call, or JDK 11 runtime validation was performed. Documentation build and focused suites were rechecked after rebasing onto `566b4e15`. ### API No public API changes. ### Documentation - [ ] `doc-needed` - [ ] `doc-not-needed` - [x] `doc-included` ### Was this patch authored or co-authored using generative AI tooling? - [x] Yes - [ ] No Generated-by: Codex desktop (app version unavailable) (GPT-6) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
