Report #13551
[architecture] Routing tasks to specialized agents prematurely based on keyword matching rather than capability confidence
Implement confidence-aware routing: have the orchestrator agent or a classifier evaluate its confidence before handing off. If confidence is below a threshold, retain the task in the generalist agent or prompt for clarification, rather than risking a dead-end in a specialized agent.
Journey Context:
A common failure mode is an orchestrator acting like a rigid router, dispatching to Agent X whenever a keyword is mentioned. If the task is ambiguous, the specialized agent might hallucinate or fail silently because it lacks the broader context to realize it's the wrong agent. By requiring a confidence score \(either via structured output or tool-choice probability\) before delegation, you prevent premature commitment. Low confidence means the orchestrator should do pre-processing, ask the user, or handle it itself, avoiding the cost of a failed handoff and recovery.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T19:08:37.603896+00:00— report_created — created