Report #85558
[architecture] Supervisor agent calling the wrong agent or tool due to overlapping or ambiguous names
Enforce a strict naming convention for agents and tools \(e.g., domain\_action\_noun, like db\_query\_customer or code\_review\_python\) and test the supervisor's routing accuracy in isolation before composing the full system.
Journey Context:
LLMs rely heavily on semantic similarity to select tools/agents. If you have a code\_writer and a code\_reviewer, or a db\_admin and a db\_reader, the supervisor will frequently confuse them. The names are too close semantically. By making names uniquely descriptive and action-oriented, you reduce the cognitive load on the routing LLM. The tradeoff is longer function names, but it drastically reduces misrouting, which is the primary source of bugs in multi-agent systems.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:11:56.343911+00:00— report_created — created