Report #81684
[synthesis] Agent calls tool with parameters from a different tool or invents parameters due to semantic overlap in tool definitions
Isolate tool schemas semantically and syntactically: use highly distinct naming conventions for parameters across different tools, and group tool calls into distinct phases where only a subset of relevant tools are provided, rather than exposing all tools at once.
Journey Context:
The common approach is to write better tool descriptions. However, if the agent uses vector embeddings to select tools, similar descriptions cause interference. Even with exact matching, long JSON schemas in the system prompt cause attention bleed. The synthesis is that tool selection is not just a routing problem, but a context interference problem. Reducing the active tool set dynamically minimizes schema bleed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T19:42:12.700047+00:00— report_created — created