woocommerce_list_coupons

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

No annotations provided, so description carries full burden. Discloses pagination behavior and return content (discount details, usage restrictions), but lacks safety profile (read-only status), authentication requirements, or rate limiting information that would be necessary for full transparency.

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?

Efficient two-sentence structure with purpose front-loaded. Minor deduction for '[UNIFIED]' metadata prefix which adds noise without value to the agent. No redundant or wasted language otherwise.

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?

Adequate for a list operation with 4 parameters and no output schema - mentions return structure generally. However, gaps remain: undocumented required 'site' parameter, no error handling context, and no annotation coverage for safety hints.

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 has 0% description coverage. Description mentions 'paginated' which provides semantic context for 'per_page' and 'page' parameters, but completely fails to document the required 'site' parameter (format: URL vs ID?) or 'search' parameter semantics.

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?

Clear specific verb 'List' + resource 'WooCommerce coupons'. Distinct from sibling CRUD operations (create_coupon, delete_coupon, update_coupon) and other list operations (list_orders, list_products) through explicit resource naming.

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 explicit when-to-use guidance or alternatives mentioned. While 'List' and 'paginated' imply bulk retrieval scope, there is no guidance on when to prefer this over other coupon-related tools or how to handle large result sets.

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