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

Goes well beyond the annotations (which only declare non-read-only, non-destructive, open-world): it discloses that future rebills are still owed and charged later, the 24-hour minimum on resume_on, the per-call confirmation default, and that the call reaches other people and requires a Cotlet API key with app access. This is rich behavioral disclosure consistent with destructiveHint=false.

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-loads the core purpose and keeps the auth/confirmation caveats at the end. Slightly repetitive ('Pause billing indefinitely...' vs 'Pauses billing of one subscription'), but nearly every sentence carries operational value.

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 mutation tool with no output schema, the description covers behavioral effects, billing edge cases, timing constraints, confirmation policy, and auth requirements comprehensively. Nothing an agent needs to invoke it correctly is missing.

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%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains the default behavior when resume_on and periods are both omitted ('lasts until you resume it') and reinforces the interaction between the two optional params.

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 ('Pause billing of one subscription') and immediately distinguishes scope from a full cancellation. An agent can tell this apart from thrivecart_cancel_subscription without opening either schema.

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?

Explains the three pause variants (indefinite, N periods, until a date) and the default behavior when neither resume_on nor periods is supplied, which is actionable usage context. It stops short of an explicit 'use this instead of cancel_subscription when...' routing statement, so it is clear but not fully differentiated against the sibling.

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