CLAUDE CODE AGENTS: FUNDAMENTALS - Chapter 2, Exercise 3 Why "Just Give It Everything" Is Flawed Reasoning ==================================================================================== QUESTION: A colleague grants a new documentation-formatting agent every available tool, including Edit and Bash, reasoning "it's simpler to just give it everything." Using this chapter's own warning box, explain why this reasoning is flawed. SOLUTION / EXPLANATION: This chapter's warning box is explicit that more tools isn't automatically more useful - granting every available tool doesn't make an agent better at the job it actually needs to do. A documentation-formatting agent's actual task is narrow: reading content and adjusting its formatting. That task doesn't require Bash (running arbitrary shell commands) at all, and Edit access beyond whatever documentation files it's meant to touch isn't needed either. Granting these tools doesn't add any real capability toward the agent's actual job - the job gets done exactly the same whether or not Bash is available, since the agent was never going to use it to format documentation correctly in the first place. What granting every tool DOES do is widen what could go wrong if something misfires - if the agent misinterprets an instruction, drifts off task, or is given an ambiguous or adversarial input, an agent with Bash access can cause damage far outside the scope of "formatting documentation," in a way an agent restricted to only the tools its job needs simply cannot, regardless of how it misbehaves. The "simpler to just give it everything" reasoning treats tool-granting as a convenience question, when this chapter frames it as a design discipline: match the allowlist tightly to what the job requires, precisely because doing so is what actually limits the damage a mistake can cause - not because it's more effort to think through which tools are truly needed. The corrected approach: grant this agent only Read and Edit access scoped to documentation files, and omit Bash and anything else its actual task doesn't call for. -------------------------------------------------------------------------- WHY THIS WORKS AS AN ANSWER: It explains specifically why the extra tools (Bash in particular) add no real capability to the documentation-formatting task at hand, then explains what they DO add (a wider blast radius for a mistake), correctly identifying "simpler" as conflating convenience with actual design discipline.