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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the HTTP verb (DELETE), the WRITE classification, and the precise source of the id, which helps the agent avoid passing code text. Adds real context beyond annotations without contradicting them.

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, mutation type and action front-loaded, then the id-sourcing caveat, then the endpoint. Nothing wasteful.

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 two-param destructive delete with full schema coverage and annotations carrying the safety profile, the description covers everything an agent needs to invoke it correctly. No output schema exists, but none is needed for a delete.

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 coverage is 100%, so baseline is 3. The description reinforces the critical gotcha (uuid id, not code text) for discount_code_id and points to the exact path, adding meaning beyond the schema's own description.

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: 'Remove a discount code from a subscription.' Clearly distinguishable from sibling apply_discount_code, and the 'WRITE:' prefix signals mutation immediately.

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?

Explicitly instructs to use the discount code id from items[].discount_codes[].id, not the code text, and names the DELETE endpoint. It gives clear invocation context but doesn't explicitly contrast when to remove vs. apply beyond the obvious inverse.

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