purchases_subscriptions_v2_cancel

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

No annotations provided, so description must cover behavioral traits. It only lists cancellationType values without explaining effects (e.g., immediate vs end-of-period cancellation, refunds). Missing details on side effects, destructive nature, and required permissions.

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?

Extremely concise: two sentences with essential information. No redundant text, front-loaded with purpose.

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 mutation tool with no output schema, description is insufficient. Missing details on parameter usage (e.g., cancelSurveyReason as an object), behavior of each cancellationType, and expected outcome.

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 covers 2 of 4 parameters with descriptions (50%). Description adds meaning for cancellationType by listing enum values, but does not explain cancelSurveyReason object. Baseline of 3 appropriate due to partial coverage; additional value is minimal.

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?

Clearly states 'Cancel a subscription' indicating verb and resource. Adds version context (2025-09+). Does not explicitly differentiate from sibling tools like revoke or defer, but the cancellationType enum clarifies the initiator.

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?

No guidance on when to use this tool versus alternatives such as revoke or defer. No context on prerequisites, timing, or exclusions.

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