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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the permission requirement (manage_woocommerce), the WooCommerce dependency, the single-page/newest-first behavior, and the AlphaBridge forwarding to one site. Return format is described inline, which compensates for the absent output schema.

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 dense sentences with zero filler: identifier, returned fields, pagination constraint, permission and prerequisite, then deployment note. Scope-critical facts are front-loaded before the forwarding detail.

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 one-parameter read-only list tool with no output schema, the description supplies the return shape, the paging limit, the auth requirement and the environment constraint. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the single per_page parameter is fully documented in the schema with range and default. The description adds nothing about per_page behavior, so the baseline 3 is appropriate — the schema does all the work.

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?

States a specific verb and resource ('list the shop's published coupons') and enumerates the returned fields (id, code, amount, discount_type, expires), which distinguishes it instantly from the write-side sibling wp_wc_create_coupon. The 'published' qualifier also narrows scope beyond the bare name.

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?

'One page only, newest first; there is no paging' tells the agent exactly how to consume the result and warns it not to attempt pagination — the key usage pitfall for a list tool. It stops short of naming an alternative tool or stating when-not to use it, so it falls just short of a 5.

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