Report #96386
[architecture] Over-engineering multi-agent systems when a single agent with tools suffices
Default to a single agent with a skill library. Only introduce multiple agents when you hit context window limits, need fundamentally different system prompts, or require isolated execution loops.
Journey Context:
Multi-agent systems introduce massive coordination overhead, state synchronization bugs, and context fragmentation. A single LLM with well-defined tools is faster, cheaper, and less prone to hallucination loops. The tradeoff is that a single agent's context window can get cluttered with tool schemas, degrading tool selection accuracy. Split when the cognitive load \(tool count \+ instructions\) exceeds what the LLM can reliably route in one context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:21:55.421602+00:00— report_created — created