Too many tools
A multi-agent system has 18 tools, and every agent was given all of them. Picks get worse, and agents reach for tools that belong to someone else's job. The tempting answers polish the tool list: better descriptions, a prompt that says “don't use these”, a router. The exam's answer is to hand out fewer tools.
D2 Tool Design & MCPExam guide 2.3About 15 minutes
Start here: the chef's counter
Picture two kitchens.
A multi-agent Claude system works the same way. A coordinator (the head chef) hands work to subagents (the stations). Each subagent's tool list is set in its AgentDefinition, the record that gives a subagent its description, its system prompt and the tools it may use. Claude picks a tool by reading the descriptions of every tool it holds, so every extra tool is one more wrong answer it could choose. A tool from another role's job is worse: the agent may use it to do that job, badly and unchecked.
The diagram follows the simulator: the counts change with how you hand out the tools.
- No, it holds many tools (18 where its job needs 4 or 5): scope its tool list to its role in its AgentDefinition.
- It uses a tool from another role's job: remove that tool. A tool it holds is a tool it may misuse, whatever the prompt says.
- It often needs one small thing from another role (a one-field lookup, many times per task): give it one narrow cross-role tool for that need, not the other role's whole set.
- The occasional hard question from another role's job: keep it going through the coordinator.
Words in the question that tell you which side you're on
Scope the tool set
- “18 tools”, “every agent gets every tool”
- “built from one template with the full tool set”
- “uses a tool outside its role”, “searches in the middle of a draft”
- “selection got worse after adding tools”
Add one limited shared tool
- “often needs to look up”, “high-frequency”
- “most checks are one-field lookups”
- “keeps handing back to the coordinator for one lookup”
- “every round trip adds a long wait”
Try it: hand out the tools
A research system has 18 tools across four roles. Pick a request, then pick how the tools are handed out. The grid shows what each agent holds; the replay shows which tool each agent calls at each step.
What each agent holds
One replay of the request
The reliability figures and minutes are illustrative, chosen to show the shape. They are not measurements. The exam guide's point is that 18 tools instead of 4 or 5 degrade selection, that agents misuse tools outside their specialisation, and that a limited cross-role tool suits a high-frequency need.
Things to try: full review + all 18 to every agent, then + scoped tools to see the misuse disappear. Then 12 checks + scoped tools to watch the round trips pile up, and 12 checks + scoped plus verify_fact. Last, one agent with all 18 on either request.
The four traps
| Trap | What the wrong option looks like | Why it loses |
|---|---|---|
| Only usually works | “Rewrite all 18 tool descriptions”; “list in each agent's prompt which tools it must not use” | Helps a little. Good labels don't fix the fact that 18 choices degrade selection, and a tool the agent holds is a tool it may still misuse. Remove it instead. |
| Overbuilt | A router agent that picks tools for the others; a hook that blocks off-role calls | Works, but adds a model call or code to maintain, plus a new failure point, when scoping the list removes the cause. |
| Too strict | No cross-role tools at all, so the agent asks the coordinator for every lookup | Correct but slow. For a frequent need the round trips add delay; a limited cross-role tool is the guide's answer. |
| Over-provisioned | “Give the synthesis agent the search agent's full tool set” to cut round trips | Solves the delay by bringing back the cause: off-role tools it can misuse. Give one narrow tool, not the whole set. |
Practice: three exam-style questions
Answer first, then open “Think it through”.
Rule to remember
Exam guide 2.3: “Too many tools (18 vs 4-5) degrades selection reliability.” “Agents with off-specialization tools misuse them.” “Scoped access; limited cross-role tools for high-frequency needs.”