wenjin272 opened a new issue, #1250: URL: https://github.com/apache/flink-agents/issues/1250
Parent: #1232 ### Problem and scope Tool Use should provide the authoritative explanation of tool declaration, parameter injection, and parallel-call behavior. Current parallelism guidance exposes internal scheduling details instead of clearly explaining the user contract. #### Scope - [ ] Keep tool declaration and use guidance coherent with Chat with Models, which introduces the chat/tool-call flow and links here for details. - [ ] Consolidate parameter-injection motivation, runtime source semantics, Java annotations, and conflict rules in Tool Use. Coordinate with #1231, where injected_args configuration shape, supported sources, defaults, constraints, and a minimal YAML example belong. - [ ] Explain parallel tool calls using enablement, defaults, and concurrency limits, including tool-call.parallelism. Verify option names and defaults against the delivered implementation. - [ ] Preserve the constraint that calls in a parallel batch must be independent and cannot wait for another call's completion. Explain that concurrency is an implementation-dependent optimization and does not guarantee overlap or ordering. - [ ] Remove unnecessary worker/continuation/slot, thread-pool, operator-subtask, and thread-reclamation details from user guidance. Coordinate concise configuration-reference descriptions and feature links with #1234. #### Coordination and acceptance Use the merged Calling LLMs structure. Coordinate the injection boundary with #1231, chat/tool flow links with the Chat with Models child of #1232, and option reference entries with #1234. Verify examples, defaults, behavioral constraints, and reciprocal links. Keep one authoritative explanation per concept. #### Review coverage DOC-050. Coordinate the Tool Use side of DOC-037 with #1231, which remains the owner of that finding. -- 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]
