wordpress_wc_create_coupon

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

The description only indicates a create operation but lacks details on side effects (e.g., whether duplicates are rejected), authentication needs, or any constraints. With no annotations available, the description carries full burden but fails to disclose expected behavior beyond the action.

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 very short (one sentence), which is concise but at the cost of essential details. It is front-loaded with the action and resource, but the brevity leaves gaps that might require additional context.

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 lack of annotations and output schema, the description should provide comprehensive context about usage, errors, and return values. It fails to do so, leaving the agent with insufficient information for correct invocation and handling.

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 input schema has 0% parameter description coverage, and the description adds no information about the 'code' or 'amount' parameters beyond their names. The meaning and format of 'amount' (e.g., numeric, currency) are not clarified, leaving ambiguity.

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 verb 'Create' and the resource 'WooCommerce discount coupon', making the tool's purpose unambiguous. It distinguishes itself from sibling tools like 'wordpress_wc_get_coupons' (reading) and other create tools by specifying the coupon context.

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 on when to use this tool versus alternatives (e.g., for bulk creation or updates). There are no prerequisites, exclusions, or context about required permissions or typical scenarios.

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