wp_woocommerce_list_orders

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

With no annotations, the description carries the behavioral disclosure burden. 'List' implies a read-only operation, and it discloses output contents and pagination support, but it does not mention authentication needs, rate limits, ordering behavior, or response format beyond the listed fields.

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 short sentences carry the essential purpose and capabilities without redundancy. Key information is front-loaded in the first sentence, making it easy for an agent to scan and understand the tool quickly.

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 simple read/list tool with fully self-documented parameters and no output schema, the description covers the core invocation details: what it lists, what fields are returned, and what query options are supported. It is slightly sparse on return-shape details but sufficient for correct selection and invocation.

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 100%, so the parameters page, status, and per_page are already documented. The description's mention of filtering by status and pagination reinforces the schema but does not add meaning beyond it, matching the baseline of 3.

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 ('List'), a clear resource ('WooCommerce orders'), and the key included data ('customer info, totals, and status'). It also distinguishes itself from single-order retrieval tools like wp_woocommerce_get_order by emphasizing plural order listing.

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?

The description implies it should be used for retrieving multiple orders and mentions filtering/pagination, but it does not explicitly state when to use it versus alternatives such as wp_woocommerce_get_order. There is clear context, but no exclusions or alternative routing.

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