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

Discloses cascade deletion, effect on chain steps (neutral on unknown ids), and studio warnings. With no annotations, this provides good insight into tool behavior, though it could mention reversibility or audit trail.

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?

Very concise, three sentences, front-loaded with the primary action and cascade effect. Every sentence adds value with no extraneous content.

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?

Given the presence of an output schema, the description appropriately focuses on input behavior and side effects. It covers delete action, cascade, and authorization. Missing details about return values are compensated by the output schema.

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 coverage is 0% and the description adds no meaning to parameters. It does not explain coupon_id or dpop_token beyond what the schema already provides (type and default). This is a significant gap.

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 clearly states the tool deletes a coupon and describes the cascade effect on patron redemptions and chain steps. Distinguishes from siblings like weather_update_coupon or weather_redeem_coupon.

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?

Explicitly states 'RESTRICTED to operator — requires proof', indicating who can use it and the prerequisite. Does not explicitly compare to alternatives or state when not to use, but the context is sufficiently clear.

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