How is a team of agents different from one agent with a large tool belt?

MCQ·Easy·4.0 · 0·~1 min·Asked atCopy Ai Mu Sigma Zoho·Relevant atMicrosoft

Attempt it

**A multi-agent system** runs two or more separate LLM-driven agents that work together on a task. Each agent has its own model call, its own prompt and persona, and its own set of tools. They coordinate by sending messages to each other, not by sharing one big prompt. The word that trips people up is multi. It means multiple agents, not multiple tools. A single agent that has access to twenty tools is still one agent: there is one LLM context per turn, one persona, one decision-maker. Add a second separate LLM context with its own role and you now have two agents. The most common multi-agent setups use role specialization. One agent plans, another researches, another writes, another reviews. Each plays a focused role with a tighter prompt and a more relevant tool set than a single jack of all trades agent could. Coordination happens through message passing managed by the runtime. Three frameworks dominate in 2026. CrewAI models a crew of role-playing agents (planner, researcher, writer). AutoGen models agents as participants in a multi-party conversation. LangGraph models the coordination as a typed state graph where nodes can be different agents. All three implement the same fundamental idea: multiple separate LLM contexts, coordinated by a runtime, talking through messages.

**A multi-agent system** runs two or more separate LLM-driven agents that coordinate, typically with distinct roles, prompts, and tool sets. They communicate by passing messages, not by sharing one prompt. Each agent has its own model context and decision boundary. The definitional line is the agent count, not the tool count. A single agent with a rich tool registry is still one agent: one LLM call per turn, one persona, one context window. The minute you spin up a second LLM call with its own role description and its own state, you have a multi-agent system. This is structural, not a matter of perceived intelligence. Multi-agent designs trade complexity for specialization. Each agent gets a tighter prompt and a more focused tool registry, which often produces better behavior than a single jack of all trades agent. Common patterns include planner-executor (one agent decomposes the task, another runs the steps), researcher-writer (one gathers, one synthesizes), and debate (two agents argue, a third decides). The cost is coordination overhead: more model calls, more orchestration logic, more places for the system to deadlock or loop. Three production frameworks dominate. **CrewAI** models a crew of role-playing agents with built-in delegation and shared memory. **AutoGen** treats agents as participants in a multi-party conversation, with a group-chat manager driving turn order. **LangGraph** lets each node in a state graph be a different agent, with explicit edges describing coordination patterns. All three implement the same fundamental pattern: separate LLM contexts coordinated by a runtime through message passing.

TL;DR

A multi-agent system runs two or more separate LLM-driven agents that coordinate via message passing, each with its own context, persona, and tool set. The 'multi' is in the agent count, not the tool count.

Memory aid

Easy to grasp

Think of a tiny office. One person can do many jobs if they have the right tools: a laptop, a phone, a calculator. That is a single agent with many tools. Now imagine the office hires a second person. They have their own desk, their own laptop, their own job description, and they can talk to the first person but they cannot read each other's minds. That is a multi-agent system. The 'multi' is about how many separate brains there are, not how many gadgets each brain has. CrewAI is like a small startup with a planner, a researcher, and a writer. AutoGen is like a conference call between specialists. LangGraph is more like a workflow diagram where each box is its own little office.

Key concepts

Multi-Agent System Coordination Agent Runtime

Concept explanation~2 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Multi-agent is one of the more hyped phrases in 2026 LLM marketing. Vendors love to claim 'multi-agent capability' because it sounds more sophisticated than 'agent'. The actual technical definition is straightforward, and once you know it you can tell which products are doing real multi-agent work and which are dressing up a single agent with a thesaurus.

This deep dive defines multi-agent precisely, distinguishes it from a single agent with a rich tool set, walks through the common coordination patterns, surveys the 2026 framework landscape, and covers the production gotchas that make multi-agent harder than it looks. By the end, you should be able to look at any agent system and decide whether 'multi' actually applies.

What multi-agent actually means

A multi-agent system runs two or more independent LLM-driven agents that coordinate to complete a task. Each agent is its own loop: its own model calls, its own context window, its own prompt and persona, its own tool registry, its own state. They communicate by sending structured messages to each other, mediated by the runtime.

The key word is independent. Two agents do not share one prompt. They might share a memory store or a coordinator, but each agent's model call sees its own context and produces its own decisions. When agent A finishes a step and hands off to agent B, agent B receives whatever messages were passed but does not inherit agent A's full reasoning trace unless that trace was explicitly serialized into the message.

This is what makes the multi in multi-agent structural rather than cosmetic. The minute you spin up a second LLM call with its own role description and its own state, you have a second agent. A single agent calling the same LLM five times in one turn (for example, with self-reflection or chain-of-thought) is still one agent because the context and persona are the same across all five calls.

Multi-agent versus a single agent with many tools

Common coordination patterns

The 2026 framework landscape

Production gotchas

Situations where this technique stops working.

2–4 min · Everything important, quickly.

Real products, models, and research that use this idea.

CrewAI: a 'crew' of role-played agents (planner, researcher, writer, reviewer) collaborating on a content task with built-in delegation and shared memory.
Microsoft AutoGen: agents as participants in a multi-party conversation, with a group-chat manager driving turn order and a Codex-style executor agent for tool runs.

What an interviewer would ask next. Try answering before peeking at the approach.

QWhen does multi-agent actually beat a single-agent design with conditional role prompting?

Multi-agent wins when roles need genuinely different prompts, different tool registries, or different underlying models. If the only difference is a section header in one big prompt, single-agent with role conditioning is cheaper and more reliable.

2 more follow-ups an interviewer would ask next. Sign in to reveal them.

Red flags & common mistakes

The phrases that signal junior thinking. Click to expand.

Most common mistake

Calling a single agent with many tools 'multi-agent'. The structural difference is separate model contexts and personas, not tool count; one LLM context window equals one agent.

60 second bullets to scan on the way to the call.

Define a multi-agent system in terms of separate LLM contexts and message passing.
Explain why a single agent with many tools is not multi-agent.

Primary sources. Browse if you want the original framing.