Report #77909
[architecture] Agent calls the wrong tool or sub-agent due to ambiguous naming in the registry
Enforce strict, unique namespacing for all tools and agents \(e.g., finance\_db\_query vs hr\_db\_query\), and dynamically filter the tool list passed to each agent to only what it strictly needs.
Journey Context:
When an orchestrator gives an agent access to 20 tools or sub-agents, LLMs suffer from tool selection degradation, often picking similarly named tools \(e.g., send\_email vs send\_email\_draft\). This is a form of accidental impersonation. The fix is two-fold: strict namespacing to reduce semantic overlap, and programmatic least-privilege \(only passing the 3-4 tools an agent actually needs for its specific step\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:21:49.841861+00:00— report_created — created