Report #7171
[architecture] Multiple agents expose identical or highly similar tool schemas confusing the orchestrator into calling the wrong agent
Namespace tools by agent and make tool names unambiguously descriptive \(e.g., database\_query vs web\_search\). Ensure the orchestrator only sees the tools it is permitted to call directly or delegate.
Journey Context:
LLMs rely heavily on function names and descriptions to choose tools. Overlapping names \(like search\) cause non-deterministic routing where the orchestrator calls the wrong agent's tool. Namespacing enforces clarity. The tradeoff is longer function names consuming slightly more tokens, but this is negligible compared to the cost of a misrouted execution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T02:05:17.550330+00:00— report_created — created