Cancel Automatic SSL subscription

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description still adds real value beyond them: durability of the action, the explicit-approval requirement, the certificates:manage permission, and idempotency-key reuse discipline. It stops short of stating the downstream effect of cancellation (e.g., what happens to the associated certificate), which keeps it from 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 compact sentences, front-loaded with the action and its prerequisites, then the durability/idempotency rule, then the permission. No filler and no repetition of schema or annotation content.

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 destructive mutation with no output schema, it covers prerequisites, approval, permissions, and retry semantics adequately. The main remaining gap is what the cancellation actually does to the subscription's certificates and whether it is reversible.

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 75%, so the schema largely documents the parameters itself, setting the baseline at 3. The description reinforces idempotencyKey semantics ('instead of using a new key') and implies the acknowledgement/approval requirement, but adds no syntax or format detail for reason or certificate_subscription_id.

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?

Specific verb+resource ('Cancel an owned Automatic SSL subscription') with the owning-scope qualifier, which cleanly separates it from cancel_certificate, cancel_free_certificate, and refresh_automatic_ssl_subscription. An agent can identify the tool's function and its target resource without opening the 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?

Explicit prerequisites: read get_automatic_ssl_subscription and list_automatic_ssl_actions first, obtain explicit approval, and hold certificates:manage. It also gives recovery guidance for the ambiguous-outcome case (refresh and read state rather than retry with a new key), which is precisely the when/when-not instruction an agent needs.

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