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

With no annotations, the description carries full burden. It discloses that removal is cosmetic, coupon still exists at operator, and patron can re-redeem later. It also states it is free. This provides useful behavioral traits beyond the name.

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?

The description is two sentences, front-loaded with the main action. Every sentence adds value with no waste.

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 tool's simplicity (removing a coupon from list) and presence of output schema, the description covers the key behavioral aspects. However, it neglects to mention dpop_token parameter, which might be important for usage.

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 0%, so description should compensate. However, it only mentions 'requires proof of npub' but does not explain npub, coupon_id, or dpop_token parameters. It adds minimal semantic value beyond the schema structure.

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 it removes a coupon from the patron's redemption list, using specific verb 'Remove' and resource 'coupon from redemption list'. It distinguishes from siblings like authority_delete_coupon by noting it is cosmetic only.

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 description provides usage context: 'cosmetic only' indicates when not to use (when permanent deletion is needed), and mentions re-redeem possibility. It also states it requires proof of npub. However, it does not explicitly name alternative tools (e.g., authority_delete_coupon) though sibling list gives that context.

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