woo_list_orders

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

No annotations provided. The description does not mention the response format, sorting, or any limits. It simply states 'list orders' with no behavioral details beyond the action.

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?

Extremely concise at 5 words, but this brevity sacrifices necessary detail. It reads more like a title than a functional description. While not verbose, it is under-speficied.

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?

No output schema, so the description should explain what the list contains (e.g., order IDs, dates, statuses). It does not. Due to the tool's simplicity and good schema coverage, more context is expected.

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 7 parameters but only 4 have descriptions. The description does not add meaning beyond the schema; it merely repeats the action. Parameters like 'per_page' and 'page' lack explanations, and the description does not fill that gap.

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 tool lists WooCommerce orders. The verb 'list' and resource 'orders' are specific, distinguishing it from sibling tools like woo_list_products or woo_list_coupons.

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 on when to use this tool versus alternatives such as woo_get_order for a single order or woo_get_customer_orders for a specific customer. No context on pagination or default behavior.

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