Report #20996
[architecture] Orchestrator agent delegates trivial, single-step tasks to sub-agents, multiplying latency and token cost
Execute deterministic or single-step logic directly within the orchestrator's tooling layer; only delegate to sub-agents for tasks requiring distinct LLM reasoning or isolated context.
Journey Context:
It is easy to over-architect by creating an agent for every capability \(e.g., 'AdditionAgent', 'FormattingAgent'\). However, every agent handoff incurs an LLM API call, latency, and context transfer overhead. If a task is deterministic \(like calling a REST API\) or requires a single tool invocation, the orchestrator should execute it directly via its own tools. Sub-agents are only justified when they need their own system prompt, custom reasoning loop, or specialized context window to handle complex, multi-step logic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:38:41.333311+00:00— report_created — created