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

Annotations already flag destructiveHint=true and idempotentHint=false, so the bar is lower; the description still adds value by naming the concrete consequence (the next order is not generated) and the human-confirmation requirement. It does not address reversibility (whether a skip can be undone) or whether the subscription must be active.

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?

Two short sentences, with the 'WRITE:' marker front-loaded so the agent immediately knows the operation class, followed by the effect and the confirmation rule. No filler.

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 single-parameter mutation whose safety profile is carried by annotations, the description covers what happens, what is affected, and the confirmation gate. Gaps remain around reversibility and error/edge behavior (already-skipped subscriptions), but nothing critical to a correct invocation is missing.

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?

Only one parameter with 100% schema coverage, and the schema already documents it including a pointer to recurpay_list_subscriptions. The description adds no syntax, format, or sourcing detail beyond what the schema provides, so the baseline 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?

States a specific verb and resource ('skip the subscription's next billing/delivery cycle') and disambiguates the effect by explaining that the next order is not generated. This is clearly distinct from sibling mutations such as recurpay_renew_subscription or recurpay_cancel_customer_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?

Provides a prerequisite ('Ask the user to confirm the subscription first') but no when-to-use versus alternatives guidance — it never says how this differs from cancelling or renewing, or what to do if the subscription is already skipped. Usage is implied rather than routed.

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