Report #55767
[architecture] Multiple agents registering the same tool name or conflicting JSON schemas, causing the orchestrator to execute the wrong function
Namespace all tools by agent ID and enforce a strict 1:1 mapping between an agent's active context and its available tool schema at execution time.
Journey Context:
In a flat tool registry, if Agent A has search\(query\) and Agent B has search\(query\) with different implementations, the LLM orchestrator will confuse them. You must scope tool definitions to the specific agent's prompt context. When control transfers to Agent A, only Agent A's tools are injected into the LLM API call. Global tool registries in multi-agent systems are an anti-pattern.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:06:00.674333+00:00— report_created — created