Resume a subscription

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

Annotations already declare that this is a non-read-only, idempotent, non-destructive mutation, so the description does not need to repeat that safety profile. The description adds useful behavioral context beyond annotations: the suspension cause, the receiver-fix prerequisite, the completed-state exclusion, and the fact that it returns the updated subscription.

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 front-loaded with the core action, then covers the suspension edge case and excludes completed subscriptions in a few compact sentences. Every clause adds a distinct operational detail.

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 tool with annotations covering safety, the description is complete enough: it states the eligible states, the blocking condition, the prerequisite check, and the return value. No output schema exists, so mentioning that it returns the updated subscription fills the gap.

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 id parameter is already richly documented with format examples and where it comes from. The description does not add parameter-specific meaning 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 states a specific verb and resource (resume a subscription) and distinguishes the eligible states from the ineligible completed state. It also names the sibling tools relevant to the exception path (send_test_event and create_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 explicitly says when to use it (paused or suspended after 20 failed deliveries) and when not to use it (completed subscriptions require creating a new one). It also supplies the prerequisite to fix the receiver first and points to send_test_event for checking.

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