Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full burden and does meaningful work: it states the proof-of-npub-ownership auth requirement and explicitly warns that deletion is 'as destructive as a write.' It does not address reversibility, idempotency, or side effects on related data, but the destructive/auth disclosure is solid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action, and each sentence adds distinct information (action, npub routing, auth/destructive warning). No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no annotations, the description covers the action, the two npub cases, and the auth/destructive profile, and an output schema exists so return values need not be explained. The remaining gap is sibling disambiguation against the dedicated delete_operator/patron_credential tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the dpop_token description is unusually thorough, so the baseline is 3. The description adds real value beyond the schema by explaining the operator-vs-patron semantics of the npub parameter, which the schema alone does not disambiguate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Delete vaulted credentials') scoped to a service and npub, which is clear on its own. However, it never distinguishes itself from the very similar siblings beesknees_delete_operator_credential and beesknees_delete_patron_credential, which appear to overlap heavily with this tool's operator/patron branches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains which npub to pass for the operator case versus the patron case, which is useful routing context. But it gives no explicit when-to-use/when-not guidance and never names the near-duplicate delete_* siblings, leaving the agent to guess whether to call this tool or those.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.