pause_subscription

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

The description adds substantial behavior beyond the annotations: the pause lasts 30 days, only one pause is allowed per 90-day cooldown, and the action requires the billing:write scope. These details help an agent understand the billing and rate-limit implications even though destructiveHint, idempotentHint, and openWorldHint are already supplied.

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 compact and front-loaded, leading with the action and duration before adding the cooldown, billing scope, and confirmation requirements. Every clause adds operational information without redundancy.

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 billing mutation with one required parameter and no output schema, the description covers the core constraints an agent needs: duration, cooldown, required scope, and explicit confirmation. It could additionally clarify post-pause behavior such as whether billing or access automatically resumes, but it is otherwise sufficient for correct invocation.

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 single confirm parameter is already well documented in the schema. The description reinforces the confirmation requirement but does not add syntax or meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: pause the authenticated user's subscription, with a 30-day duration and cooldown constraint. This clearly distinguishes it from sibling subscription tools such as cancel_subscription, resume_subscription, and upgrade_subscription.

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?

It gives clear usage context: this is a billing action requiring billing:write and should only be called after explicit user confirmation. It does not explicitly name alternative subscription tools or state when not to use this one, but the confirmation prerequisite is a strong usage constraint.

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