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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly warns that deletion is 'as destructive as a write' and states that proof of npub ownership is required, which informs the agent about severity and authentication. It could additionally mention irreversibility or side effects, but it already goes well beyond a generic mutation description.

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?

Two short sentences front-load the core action and then provide essential usage caveats. Every sentence earns its place with no redundant 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?

Given the rich dpop_token schema, 100% schema coverage, and an output schema, the description covers the critical destructive nature and operator/patron distinction well. The main gap is not acknowledging the closely related sibling delete tools, which would make the tool selection unambiguous.

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 description coverage is 100%, so the baseline is 3; the description adds extra meaning by distinguishing operator vs patron npub semantics and by emphasizing the proof requirement tied to the dpop_token. That raises it above baseline.

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 clearly states the action ('Delete vaulted credentials') and the target ('specific service and npub'), making it a distinctive verb+resource pairing. However, it does not explicitly differentiate itself from the closely named sibling tools authority_delete_operator_credential and authority_delete_patron_credential, so an agent could initially confuse them.

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 concrete usage context: for operator credentials pass the operator's npub, for patron credentials pass the patron's npub, and proof of ownership is always required. But it never names or contrasts with the sibling delete tools, leaving the when-to-use-this-vs-alternative decision implicit.

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