Report #61951
[architecture] Agents hallucinating tool calls or calling the wrong tool due to overlapping schemas
Namespace all tools and ensure tool schemas are strictly scoped to the agent that owns them; do not inject the global tool list into every agent's prompt.
Journey Context:
If Agent A has search\(query\) and Agent B has search\(database\_query\), and the orchestrator passes both schemas to a routing LLM, the LLM will confuse them. Tools must be strictly bound to the agent that executes them. The orchestrator should only see agent descriptions, not their internal tool schemas, unless routing specifically requires it, to prevent schema collision and selection errors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:28:15.391972+00:00— report_created — created