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

No annotations are provided, so the description carries the full behavioral burden. It discloses destructive deletion of every stored model, reinitialization behavior with all tools at 0 sats, the return value, and the nsec-signed operator proof requirement. It does not explicitly state irreversibility or confirmation behavior, but most critical traits are covered.

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 front-loaded and concise, using four short lines with no filler. 'Returns the new model' is slightly redundant with the output schema but does not harm readability.

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 restricted destructive tool with one parameter and an output schema, the description covers key risks and the outcome. The undocumented dpop_token parameter and lack of alternative guidance are clear gaps, but the output schema handles return values.

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 0% and the single parameter dpop_token is never mentioned. The description mentions an nsec-signed proof, but does not map this to dpop_token or explain the token's role, leaving the parameter effectively undocumented.

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: erase all pricing models and restore a viable default. This distinguishes it clearly from sibling tools like get_pricing_model and set_pricing_model.

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 operator restriction and nsec-signed proof requirement are explicit prerequisites. However, it does not say when to use this instead of set_pricing_model or get_pricing_model, so alternative selection is only implied.

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