Deletes a paywall coupon

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds 'Changes community state' and the confirm gate, but says nothing about reversibility, side effects on existing redemptions, or failure conditions beyond what annotations imply.

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 no filler, and the behavioral constraint follows immediately after the purpose. The first sentence largely restates the title, so it is efficient but not maximally informative per word.

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, non-idempotent mutation with no output schema, the definition covers the essentials (what is deleted, the confirm requirement) but omits consequences an agent would want — whether deletion is permanent, what happens to subscribers on the coupon, and what the response contains.

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% — id, account, and confirm are each documented inline, including the 'named private Circle account' nuance. The description adds no parameter-level meaning beyond the schema, 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?

The description states a specific verb and resource ('Deletes a paywall coupon'), which is unambiguous and clearly distinct from nearby siblings like delete_paywall or delete_post. It does not, however, contrast itself with any related coupon tool or explain the scope of the deletion.

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 gives one concrete precondition — 'requires confirm=true for the user-requested action' — which steers invocation but leaves the agent to infer when a coupon deletion is appropriate. No alternative or exclusion is named, and no prerequisite (e.g. coupon must be unused) is given.

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