Report #37858
[architecture] Giving multiple agents tools or sub-agents with identical names or overlapping descriptions, causing the orchestrator LLM to route to the wrong entity
Enforce strict, globally unique, and semantically distinct names/descriptions for all agents and tools across the entire fleet.
Journey Context:
LLM routing relies heavily on name and description matching. If Agent A has 'search\_db' and Agent B has 'search\_database', the router will arbitrarily choose. Tradeoff: highly specific names reduce composability but are strictly necessary for LLM function-calling reliability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T18:01:36.137300+00:00— report_created — created