Report #7797
[architecture] LLM router invokes the wrong agent or tool because multiple agents expose identically named functions
Enforce strict global namespacing for all agent tools and capabilities \(e.g., 'refund\_agent\_process\_refund' instead of 'process\_refund'\) across the entire multi-agent system.
Journey Context:
LLMs select tools based on name and description. If Agent A \(Sales\) and Agent B \(Support\) both expose a 'lookup\_user' function, the orchestrator will inevitably route to the wrong one, causing capability errors. Namespacing makes the domain explicit. Tradeoff: longer function names consume slightly more prompt tokens, but this is negligible compared to the cost of executing a tool in the wrong context and having to rollback/compensate.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T03:44:27.966416+00:00— report_created — created