WooCommerce: List coupons

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds that results are paginated and what categories of data are returned, which is useful beyond the annotations, but it does not disclose default page size, total-count behavior, or whether an unbounded listing is expensive.

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?

Two sentences, front-loaded with the action and followed by the return shape; nothing is padded. The only weakness is that the terse second sentence packs several claims without elaborating on any of them.

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 read-only list tool with no output schema, an agent still lacks the default page size, the result ordering, and what the search field matches. The description is adequate to identify the tool but thin on the operational details needed to call it confidently.

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%, so the description carries the parameter burden, and it partially does: "paginated" signals the page/per_page pair and "discount details and usage restrictions" hints at what the payload contains. It does not explain what the search parameter matches against or why site is required.

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 states a specific verb and resource ("List WooCommerce coupons") and adds what comes back ("paginated coupon list with discount details and usage restrictions"). It does not explicitly contrast itself with woocommerce_create_coupon or woocommerce_delete_coupon, but the verb alone separates reads from the mutation siblings.

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?

There is no statement of when to choose this tool versus any alternative — no mention of how to narrow results, no guidance on when a filtered or single-coupon lookup would be preferable. The only hints are implicit in the words "list" and "paginated", so usage must be inferred.

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