Report #40369
[frontier] One powerful model doing everything in agent system is too expensive and slow for simple sub-tasks
Use the Agent-as-Tool pattern with model tiering: wrap specialized sub-agents as tools that a coordinator agent invokes. Assign cheaper, faster models to sub-agents and reserve the expensive model for the coordinator that makes high-stakes decisions and synthesizes results. The sub-agent runs to completion and returns a structured result—the coordinator retains control throughout.
Journey Context:
The naive approach runs one powerful model for everything—including simple formatting, data extraction, and classification tasks where a smaller model suffices. This wastes money and adds latency. The Agent-as-Tool pattern lets you right-size: the coordinator uses a capable model for planning and synthesis, while sub-agents use cheap models for narrow tasks. This is different from handoff \(where control transfers permanently to the next agent\). The key tradeoff: sub-agents can't ask the coordinator clarifying questions mid-execution, so their task scopes must be well-defined and self-contained. But for parallelizable work—analyze three documents simultaneously, classify ten items—this pattern is dramatically faster and cheaper than sequential processing on one expensive model. Production teams report 5-10x cost reduction with equivalent or better output quality when sub-tasks are well-scoped.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T22:13:53.722153+00:00— report_created — created