woocommerce_list_orders

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior and the general structure of returned data (customer details, totals, status). However, it lacks information on rate limits, authentication requirements, error behavior for invalid sites, or whether this is a read-only safe operation.

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 compact at two sentences and front-loads the core action. The '[UNIFIED]' tag appears to be metadata noise but doesn't significantly detract. Given the lack of schema documentation, however, it may be overly terse rather than appropriately concise.

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 7 parameters including date range filters, status filters, and customer filters, the description is incomplete. It fails to document the filtering capabilities (after, before, status, customer) which are significant behavioral features. No output schema exists to compensate for the lack of return value description.

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?

With 0% schema description coverage across 7 parameters, the description fails to compensate adequately. The mention of 'paginated' implicitly hints at 'page' and 'per_page' parameters, but provides no explanation for the required 'site' parameter, filtering parameters ('status', 'customer', 'after', 'before'), their formats, or valid values.

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 action 'List WooCommerce orders' and specifies the return content (paginated list with customer details, totals, status). The '[UNIFIED]' prefix is noise but the core purpose is specific. It implicitly distinguishes from sibling 'woocommerce_get_order' by being a list operation, though it doesn't explicitly contrast them.

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 provided on when to use this versus 'woocommerce_get_order' (for single order retrieval) or other order-related tools. No mention of prerequisites like site authentication or when filtering is preferred over fetching all orders.

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