Report #77505
[architecture] When to use multi-agent vs single-agent with tools
Default to a single agent with a skill/tool library. Only introduce multiple agents if you need strict context isolation, distinct system prompts that conflict, or parallel execution of independent tasks.
Journey Context:
Multi-agent systems are often over-engineered. A single agent maintains a unified mental model and avoids the token overhead and error rates of inter-agent communication. The tradeoff is that a single agent can suffer from tool-choice confusion if the tool library gets too large, or context window limits if the task is too broad. Multi-agent is only justified when the cognitive load or security boundaries strictly require partitioning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:41:37.592629+00:00— report_created — created