wp_woocommerce_list_coupons

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'List' and gives output fields. It does not state that the operation is read-only, how pagination works, what permissions are needed, or whether 'all' means one page or multiple pages given the per_page default of 20.

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 a single front-loaded sentence with no filler, naming action, resource, and output content. It could have added a short pagination qualifier to remove ambiguity, so it is not a perfect 5.

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 tool with one optional parameter, this is mostly adequate: the resource, output fields, and default are covered between description and schema. However, without annotations or an output schema, it lacks explicit response-shape, authentication, and pagination behavior, so it is only minimally complete.

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 already fully documents per_page with a default, so the description adds little parameter-level meaning. 'List all coupons' hints at pagination scope but not precisely enough to raise the score above the baseline for high schema coverage.

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 names a specific verb and resource ('List all WooCommerce coupons') and lists the meaningful output dimensions (discount types, amounts, usage stats). This is enough for an agent to distinguish it from sibling tools such as wp_woocommerce_create_coupon or wp_woocommerce_status.

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?

Usage context is only implied by the verb and resource; there is no explicit statement about when to prefer this over wp_woocommerce_stats or wp_woocommerce_create_coupon, nor any exclusion criteria. It is minimally usable but leaves the routing decision to inference.

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