wordpress_wc_create_coupon

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't disclose what permissions are required, whether the coupon becomes active immediately, what happens if a coupon with the same code exists, or what the response looks like. For a creation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise at just four words, with zero wasted language. It's front-loaded with the essential action and resource. Every word earns its place, making it easy to parse while conveying the core purpose.

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 creation tool with 2 required parameters, 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain parameter semantics, behavioral implications, usage context, or what to expect upon success/failure. The conciseness comes at the cost of completeness for this moderately complex 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?

The schema has 0% description coverage, so both parameters (code and amount) are completely undocumented in the schema. The description doesn't add any parameter information - it doesn't explain what format the code should be, what the amount represents (percentage, fixed amount, currency), or any validation rules. This fails to compensate for the schema's lack of documentation.

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 action ('Create') and resource ('WooCommerce discount coupon'), making the purpose immediately understandable. It distinguishes this from general WordPress tools but doesn't explicitly differentiate it from sibling WooCommerce tools like 'wordpress_wc_create_product' or 'wordpress_wc_get_coupons' beyond the obvious creation vs retrieval distinction.

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 is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (like WooCommerce being active), appropriate contexts, or what happens after creation. While the name implies it's for WooCommerce coupons, there's no explicit usage context or comparison to other coupon-related tools.

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