Report #81991
[frontier] Single monolithic agent becomes unreliable as tool count and capability scope grow
Spawn short-lived, single-purpose micro-agents for each subtask with narrow system prompts and 1-3 tools each. Use handoff tools to transfer control between specialists. Discard agents after task completion
Journey Context:
The instinct is to build one powerful agent with many tools and a long system prompt. This degrades because tool selection accuracy drops with more options \(studies show significant degradation beyond ~10 tools\), context gets polluted with irrelevant task history, and one failure cascades through the entire session. The emerging pattern \(demonstrated by OpenAI's Swarm\) uses lightweight orchestrators that hand off to specialist agents. Each specialist has a narrow scope, minimal tools, and a focused system prompt. When done, control returns via handoff. Key implementation detail: the handoff itself should be a tool the agent can invoke \(e.g., transfer\_to\_coding\_agent\(reason, context\)\), not external orchestration logic. This makes the control flow visible in the agent's reasoning. Tradeoff: more total LLM calls and higher latency per workflow, but dramatically higher per-task success rates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T20:13:07.786027+00:00— report_created — created