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

Annotations already set destructiveHint to true. The description adds valuable detail: explains what destruction means in this context (turns off auto-renew, prevents further billing, existing paid periods remain valid). This goes beyond the annotation and fully discloses the behavioral implications.

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 extremely concise, consisting of three short sentences. It front-loads the key action and each sentence provides unique value: action, destructive nature, and the effect on billing and existing periods. No waste.

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 simple, one-parameter destructive operation with an existing output schema and clear annotations, the description covers essential behavioral aspects. It lacks mention of prerequisites (e.g., having an active subscription) but is otherwise sufficient.

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% with the subscriptionId parameter already described as 'Subscription ID'. The description adds no additional parameter-level detail beyond what the schema provides. Baseline score of 3 is appropriate.

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 tool cancels a subscription and specifies that it turns off auto-renew, preventing future billing. It implicitly distinguishes from sibling tools like pause_subscription by labeling it 'Destructive', indicating permanent action.

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 clear context for use (final cancellation of auto-renew and billing) but does not explicitly mention when not to use it or name alternative tools such as pause_subscription or resume_subscription. The destructive label helps, but explicit guidance would improve.

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