Suspend a subscription (write)

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

No annotations are provided, so the description carries the behavioral burden. It clearly discloses that this is a WRITE operation, that a suspended subscription stops granting rights and stops being billed, that it is not terminated, and that get_usages should be re-read afterward. Missing specifics like permissions or response shape prevent a 5.

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?

Three tight sentences front-load the WRITE nature and core behavior. Every sentence adds value: what suspension means, how it differs from termination, and what to do afterward.

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 one-parameter mutation with no output schema and no annotations, the description covers the operation, its behavioral effects, sibling distinctions, and a follow-up action. It does not describe the response payload or authorization requirements, but these are not essential for selecting and invoking this tool correctly.

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 input schema already documents subscription_id as the internal identifier from list_subscriptions. The tool description adds no parameter-level semantics beyond the schema, 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 uses a specific verb and resource: 'Suspends a ProAbono subscription.' It also distinguishes the operation from terminate_subscription and connects it to start_subscription, so an agent can tell it apart from sibling subscription tools without opening their schemas.

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 names the two closest alternatives, start_subscription and terminate_subscription, and explains the key distinction: suspension is reversible and not a termination. It stops short of an explicit rule like 'use terminate_subscription for permanent cancellation,' but the routing is strongly implied.

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