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

With no annotations provided, the description carries the full safety burden and explicitly warns that deletion is 'as destructive as a write' and that proof of npub ownership is always required. This is substantive and helps an agent treat the operation as sensitive. It could add explicit irreversibility details, but the disclosed destructive/auth profile is strong.

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 with no filler: core action first, then operator/patron clarification, then the safety warning. Every sentence earns its place.

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 three-parameter tool with a rich input schema and an output schema present, the description covers what is deleted, who can be targeted, and the proof/auth requirement. The main missing piece is explicit tool-selection guidance relative to the delete_*_credential siblings, but the direct call requirements are otherwise complete.

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?

The input schema already documents all three parameters at 100% coverage, including a detailed dpop_token format, so the baseline is 3. The description adds operator-vs-patron meaning for npub, but it does not add substantive meaning for service or dpop_token beyond the schema.

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?

The description states a specific action ('Delete vaulted credentials') and resource ('for a specific service and npub'), so it is far from a tautology. It adds operator/patron nuance, but it does not explicitly distinguish this tool from the sibling roastify_delete_operator_credential and roastify_delete_patron_credential tools.

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 gives clear usage context: pass the operator's own npub for operator credentials and the patron's npub for patron credentials, and always require proof of npub ownership. However, it names no alternatives and gives no exclusions, leaving the relationship to the credential-deletion siblings ambiguous.

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