Pay: subscriptions delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantive context beyond them: it deletes user links too, it does NOT cancel at Stripe/Apple so the customer can still be billed, and it is a recovery tool for stuck/duplicate records. This is exactly the extra behavioral detail annotations cannot convey.

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?

Front-loaded with the core action and scope, and the consequences/alternatives follow in a logical order. The closing sentence ('It changes or deletes existing data, so check with the user') is mildly redundant with destructiveHint=true, keeping it just short of a 5.

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 single-param destructive mutation with annotations and no output schema, the definition covers purpose, prerequisites, billing side effects, and the correct alternative tool. An agent has everything needed to invoke it responsibly.

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 100% and the schema itself tells the agent the id is a guid discoverable via pay_subscriptions_list. The description adds no parameter-level detail, so the baseline of 3 is correct when the schema carries the full burden.

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?

States a specific verb and scope: 'Hard-delete a subscription (project admin)' plus the exact purpose ('permanently removes a stuck or duplicate subscription record and its user links'). It is clearly distinguishable from the sibling pay_subscriptions_cancel, which it names explicitly.

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 gives the when-to-use case (stuck or duplicate subscription record) and the when-not/alternative case ('use pay_subscriptions_cancel first if billing should stop'). Nothing is left to inference.

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