Pay: subscriptions resume

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

Goes well beyond the annotations by disclosing the real consequence: the subscription renews and the customer is charged again at period end. That financial side effect is the key thing an agent must know before invoking this non-read-only tool. It does not cover failure modes (e.g., behavior when no cancellation is scheduled), which keeps it short of 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-loaded with what the tool does, then the side effect, then the routing guidance. Every sentence earns its place with no restatement of the name or annotations.

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 state-change tool with no output schema, the description supplies purpose, mechanism, side effect, and the alternative tool — everything needed to call it correctly and safely.

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 documented as a guid with a discovery path via pay_subscriptions_list. The description adds no further meaning about the identifier, so the baseline of 3 applies.

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 (resume) plus resource (cancelled subscription), with the underlying mechanism spelled out: it removes a scheduled cancellation on a Stripe subscription. It is unmistakably distinct from pay_subscriptions_cancel and pay_subscriptions_force_expire among the many pay_* siblings.

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?

Names the exact sibling it inverts ('undo `pay_subscriptions_cancel`') and states the timing constraint ('before the period ends'), so the agent knows both the alternative and the window in which this tool is the right choice.

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