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

Annotations already flag destructiveHint=true, so the description's 'Destructive' label is redundant, but it adds valuable context: what gets destroyed (auto-renew and future billing) and what persists (existing paid periods stay valid). This goes beyond the annotations and does not contradict 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?

The description is compact: two sentences, front-loaded with the primary action, followed by key consequences. Every sentence adds value and there is no filler or restatement of the tool name.

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 single-parameter mutation with an output schema and annotations, the description covers the essential behavioral outcomes clearly. The only gap is the lack of explicit guidance on how this relates to pause_subscription, but overall it is sufficiently complete.

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 fully documents the single parameter subscriptionId with 100% coverage. The description adds no additional parameter-level semantics, so it receives the baseline score for high schema coverage.

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 verb and resource: 'Cancel a subscription.' It adds specific behavioral details (turns off auto-renew, prevents further billing cycles) that clarify the operation. However, it does not explicitly distinguish itself from the sibling tool pause_subscription, so it falls short of a 5.

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 implies when to use this tool by emphasizing its destructive, terminal nature ('prevents further billing cycles'), which helps differentiate from a pause. However, it does not explicitly state when not to use it or name alternatives such as pause_subscription, leaving the when-to-use guidance implicit.

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