Report #87076
[architecture] Orchestrator routing to the wrong agent due to overlapping tool descriptions
Namespace tools strictly by agent domain and ensure mutually exclusive responsibilities. If Agent A searches the web and Agent B searches the database, name their tools \`web\_search\` and \`internal\_db\_query\` with highly distinct descriptions.
Journey Context:
LLM routing relies heavily on semantic similarity between the user prompt and tool/agent descriptions. If multiple agents have similarly described capabilities, the router will frequently misroute. Distinct, namespaced descriptions reduce the search space confusion. The tradeoff is that it limits cross-agent tool sharing, requiring duplication or proxying if an agent genuinely needs another's tool.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T04:44:50.279039+00:00— report_created — created