woocommerce_delete_coupon

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

With no annotations provided, the description carries the full burden. It discloses the dual behavioral modes (force delete vs. trash), but fails to mention reversibility, side effects if the coupon is in use, or what the return value/response looks like.

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 efficiently structured in two sentences with the action front-loaded. However, the '[UNIFIED]' prefix appears to be metadata noise that doesn't aid agent understanding, slightly reducing the score.

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 deletion tool with 3 parameters, no output schema, and zero annotations, the description provides minimum viable information about the core action but leaves critical gaps in parameter documentation and behavioral outcomes (e.g., error handling, what happens if coupon doesn't exist).

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%, requiring the description to compensate. While it explains the 'force' parameter's behavior (force delete vs trash), it completely omits semantics for 'site' (URL? Site ID?) and 'coupon_id' (WooCommerce internal ID?), leaving two of three parameters undocumented.

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 specific verb (Delete) and resource (WooCommerce coupon), distinguishing it from sibling tools like woocommerce_create_coupon or woocommerce_delete_product by explicitly naming the resource type.

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 hints at usage patterns by mentioning 'force delete or move to trash,' implying when to use the force parameter. However, it lacks explicit guidance on when to use this tool versus update_coupon, or prerequisites like needing the coupon_id.

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