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

Annotations only give destructiveHint=true; the description adds real context beyond that by stating it modifies live data, stops future charges, that cancellation_reason is mandatory, and the exact REST call and body shape it maps to. It does not cover reversibility or what happens to in-flight shipments, keeping it out of 5 territory.

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 action and impact, then the operational details, all in a compact block. The caps/backtick styling and REST endpoint detail are marginally noisy but each sentence carries information.

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?

No output schema exists, yet the description discloses the return shape ('Returns { subscription }'), covers all parameters, and the destructive annotation covers the safety profile. Missing only edge-case behavior such as irreversibility or timing of the cancellation, so it is nearly complete rather than fully so.

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%, so all three parameters are already documented including the required flag. The description only restates that cancellation_reason is required, adding no format, allowed values, or guidance beyond the schema – the baseline 3.

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 resource ('CANCELS an active subscription'), plus the concrete effect ('stops all future charges'), which cleanly separates it from sibling recharge_activate_subscription. The scope qualifier 'active' also tells the agent which subscriptions are eligible.

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 'active subscription' qualifier implies a precondition, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., activate to reverse, skip_charge for deferral). Usage is inferable rather than stated.

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