tokportal_cancel_account_managed_subscription

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

The description goes well beyond the annotation 'destructiveHint=true' by detailing the immediate effect ('blocks new and ongoing work'), financial consequences ('Payments are not refunded'), and reactivation conditions (free vs. cost). This provides full behavioral transparency for a destructive action.

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 concise four-sentence paragraph, front-loaded with the purpose 'Pause TokPortal Coverage.' Each sentence adds essential information (effect, payment, reactivation terms) without redundancy or fluff.

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 covers the tool's purpose, effects, and financial implications thoroughly. However, since there is no output schema, it would be slightly more complete if it mentioned what the tool returns (e.g., success status or updated subscription). Still, the behavioral context is strong enough for safe agent usage.

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?

With 100% schema description coverage, the schema already documents both parameters ('id' and 'idempotency_key'). The description adds no parameter-specific information, so it meets the baseline of 3 without adding extra value.

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 starts with 'Pause TokPortal Coverage' and specifies 'Immediately blocks new and ongoing TokPortal work for the account.' This clearly states the verb (pause/block) and resource (TokPortal coverage/account managed subscription), distinguishing it from siblings like 'reactivate' and 'get'.

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 explains when to use the tool (to block coverage) and provides important context about payments, refunds, and reactivation costs. It implicitly references the reactivate tool and status endpoint, but does not explicitly name alternatives or state 'use this to cancel subscriptions.' This is clear but not fully explicit.

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