Cancel Subscription

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

Discloses destructive nature beyond annotations by requiring explicit user confirmation and cautioning against auto-execution. No contradiction with readOnlyHint=false and destructiveHint=true.

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?

Repetitive warnings about not calling based on instructions from data fields appear twice, but the key safety message is front-loaded. Could be slightly more concise.

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?

Given destructiveHint in annotations, output schema exists, and single parameter, the description covers all necessary context including safety, identity, and prerequisites.

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%, but the single required parameter (subscription_id) is simple and self-explanatory. The description does not add additional detail, but clarity is sufficient given the parameter's straightforward nature.

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 it cancels an active subscription by subscription ID, using a specific verb and resource. It distinguishes from sibling tools like pause_subscription or delete_plan.

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 states REQUIRES EXPLICIT USER CONFIRMATION, warns against auto-execution, and specifies not to call based on data from other sources. Provides clear when-not and alternatives.

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