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

With no annotations provided, the description carries full burden. It details destructive behavior: 'Erase all pricing models', 'Deletes every stored model', then 'self-initializes a fresh one'. Also mentions authentication requirement and return value. Discloses key traits adequately.

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?

Description is concise (three sentences) with front-loaded action statement. Uses bold for emphasis ('RESTRICTED') and avoids unnecessary words. Every sentence adds value.

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?

Exists output schema presumably documenting return value, so less burden on description. The tool is complex (destructive reset), and description covers main aspects but omits parameter explanation and irreversibility warning. Adequate but with gaps.

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%, yet the description does not explain the 'dpop_token' parameter. While 'requires proof (nsec-signed)' hints at its purpose, the parameter is not directly described. Agents cannot understand what to pass, degrading usability.

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?

Description clearly states verb 'Erase' and 'restore' with resource 'pricing models'. It differentiates from siblings like taxsort_get_pricing_model and taxsort_set_pricing_model by explaining it deletes all stored models and initializes a default. Purpose is specific and distinct.

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?

Description notes it is 'RESTRICTED to operator — requires proof (nsec-signed)', indicating usage context. However, it does not explicitly state when to use vs alternatives like taxsort_set_pricing_model. Provides clear context but lacks explicit exclusions.

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