resume_subscription

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description's contribution is the billing-state effect and the auth scope requirement, both of which are genuinely additive. It stops short of describing what happens on a non-paused subscription or what the response contains, but the key behavioral consequence is disclosed.

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?

A single tightly-packed sentence: the action, the scope of the target, the effect, and the auth requirement, with the action front-loaded. No filler and nothing that could be trimmed without losing information.

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 zero-parameter state-transition tool with no output schema, the description covers the essentials: what changes, whose subscription, and the required permission. A brief note on failure modes (not paused, no active subscription) would make it fully self-sufficient.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to carry; the baseline for a no-param tool applies. The description correctly implies the target subscription is derived from the authenticated user rather than passed in.

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 ('Resume') and a specific resource ('the authenticated user's paused posterly subscription'), plus the immediate consequence ('restoring active billing'). It is clearly distinguishable from siblings such as pause_subscription, cancel_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?

The precondition is explicit: the subscription must be 'paused', and the required 'billing:write' scope is named, which tells an agent when this call is applicable and what it needs. What's missing is guidance for the edge cases — what to do if the subscription is not paused, canceled, or nonexistent — with no explicit pointer to get_subscription to verify state first.

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