tokportal_cancel_account_managed_subscription

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

Annotations already indicate destructiveHint=true, and the description adds valuable context: the immediate blocking of work, non-refundable payments, and the conditions for reactivation costs. This goes beyond the annotation by specifying what exactly gets blocked and the financial implications, which helps the agent understand the full behavioral impact.

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 four sentences, front-loaded with the title 'Pause TokPortal Coverage'. Every sentence adds distinct value: purpose, immediate effect, refund policy, and reactivation costs. No redundant or unnecessary 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?

The description covers the immediate effects and financial policy, which is adequate for a mutation tool with no output schema. However, it lacks detail on the state the account enters after pausing, whether existing settings are preserved, and the full lifecycle (e.g., what 'reactivation' entails beyond cost). This leaves some gaps for an AI agent.

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% with both parameters (id and idempotency_key) already described clearly in the input schema. The description does not add any additional meaning or context about the parameters, so it meets the baseline but does not exceed it.

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 clearly states the tool's purpose as 'Pause TokPortal Coverage' and explains it blocks new and ongoing work. The verb 'Pause' and resource 'Coverage' are specific, but the description does not explicitly distinguish from sibling tools like get_account_managed_subscription or reactivate_account_managed_subscription, though the name and title imply it is the cancel action.

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 context about when reactivation is free vs costly, implying usage scenarios. However, it does not explicitly state when to use this tool versus alternatives (e.g., when to cancel vs reactivate), nor does it mention any prerequisites or contraindications. The sibling list includes get and reactivate, but the description does not reference them.

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