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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It clearly warns that deletion is destructive and that proof of npub ownership is always required. It could go further on irreversibility or side effects, but the destructive/auth context is significantly better than a bare 'delete' statement.

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?

The description is compact and front-loaded with the primary action. Each sentence earns its place: the purpose, the npub selection rule, and the critical destructive-auth warning. No fluff or redundant schema repetition.

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?

The description covers the essential destructive nature and authentication requirement, and an output schema exists so return-value documentation is not needed. However, the presence of sibling tools like taxsort_delete_operator_credential and taxsort_delete_patron_credential creates real ambiguity about which endpoint to call, and the description does not resolve it.

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 has 100% coverage with detailed descriptions, so the baseline is 3. The description adds value by clarifying the operator-versus-patron meaning of the npub parameter and reinforcing the dpop_token proof requirement. This goes beyond simply restating 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 clear action ('Delete vaulted credentials') with a specific resource scope ('for a specific service and npub'). It is not a tautology and conveys the tool's core operation, but it does not distinguish it from closely named siblings like taxsort_delete_operator_credential and taxsort_delete_patron_credential.

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?

The description provides useful context about when to pass an operator's npub versus a patron's npub and stresses that proof of ownership is required. However, it does not explain when this tool should be chosen over the similarly-purposed sibling delete/forget tools, leaving the selection decision somewhat ambiguous.

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