CHAPTER 03 · Tool Design · 11 / 11
A checklist for a well-designed tool
- Does its name map to a recognisable user-level action?
- Does its description say when and how to use it, not just what it does?
- Does it chain to related tools where relevant?
- Is there a cheaper variant for the common case?
- Can the model batch when it needs many?
- Is the schema tight (enums, bounds, required, field descriptions)?
- For formatted output, does it take structured input?
- Does its result return useful errors and distilled (not dumped) data?
- Is it offered only on surfaces where it makes sense?