woocommerce_create_coupon

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

With no annotations provided, the description carries full behavioral burden. It discloses supported discount types and restriction capabilities, but lacks critical mutation details: idempotency behavior (duplicate code handling), required permissions, or return value structure.

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?

Efficient two-sentence structure with action front-loaded. The '[UNIFIED]' prefix appears to be metadata leakage but doesn't significantly impede readability. No redundant or wasted language.

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?

Inadequate for a 15-parameter mutation tool with no output schema and no annotations. Missing return value description, error handling specifics, and critical parameter formats needed to successfully invoke the tool.

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 has 0% description coverage for 15 parameters. The description compensates partially by grouping parameters functionally (discount types, usage limits, restrictions), but fails to document critical required fields ('site', 'code', 'amount') or formats (e.g., comma-separated product_ids, date format for expires).

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?

Clear verb ('Create') and resource ('WooCommerce coupon') with specific capability details (percentage/fixed discounts, usage limits). Distinguishes from sibling list/update/delete tools by specifying 'new' creation, though lacks explicit contrast with woocommerce_update_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?

No guidance on when to use this tool versus alternatives (e.g., when to create new vs. update existing, or prerequisites like checking if coupon code exists). Missing selection criteria for the 15-parameter configuration.

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