revoke_subscription_purchase

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

No annotations are provided, so the description must carry the full burden. It indicates a refund action but fails to disclose side effects (e.g., user loses access, refund is irreversible) or any required permissions. With no annotations, this is minimal disclosure and insufficient for a mutating operation.

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 a single succinct sentence with no fluff or redundancy. It front-loads the key action and object, making it easy to scan. No unnecessary words.

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?

The description is extremely brief and omits critical context such as effect on the subscription, whether the refund is reversible, or any required authentication or permissions. With no annotations and an output schema not described, the tool is under-specified for an agent to safely invoke it without additional context.

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% (all 3 parameters have descriptions in the schema), so the description adds minimal value beyond what the schema provides. The description implies refund_type behavior but doesn't elaborate beyond the schema's 'default: full' note. Baseline 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?

Description clearly states the action ('Revoke (refund)') and the resource ('a subscription purchase'), using specific verb+resource. It distinguishes from similar tools like cancel_subscription_purchase and refund_order by explicitly mentioning 'refund' and 'subscription purchase', though it doesn't elaborate on the differences.

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 no usage context, alternatives, or exclusions. It does not explain when to use this tool vs cancel_subscription_purchase or refund_order, nor any prerequisites or conditions. Only the name and brief description hint at usage.

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