Report #12468
[architecture] Orchestrator invoking the wrong agent tool due to identical function names across different agents
Namespace all tools and skills by agent or domain \(e.g., db\_query vs api\_query\) at the registry level before presenting them to the LLM.
Journey Context:
When composing agents from different libraries or teams, tool name collisions are inevitable \(e.g., multiple agents exposing a search tool\). LLMs will arbitrarily pick one based on semantic proximity, often choosing the wrong one. Namespacing tools ensures unambiguous dispatch and prevents the orchestrator from confusing a local file search with a web search.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T16:09:34.635936+00:00— report_created — created