List orders

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

No annotations are provided, so the description must carry the full burden. It mentions ordering and filtering, but does not disclose whether the operation is read-only, rate limits, or authentication requirements. The description is adequate but not fully transparent.

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 very concise (one sentence, 8 words) and front-loaded with the verb and resource. Every word adds value with no redundancy.

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?

Given the tool's simplicity (2 params, no required params, no output schema, no annotations), the description covers the essential purpose, ordering, and filtering. It is nearly complete, only lacking explicit mention of pagination behavior.

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?

The schema provides full coverage for both parameters (100% schema_description_coverage). The description adds ordering behavior ('newest first') that is not in the schema, and confirms the filtering capability of the 'status' parameter. However, 'per_page' is not mentioned in the description.

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 verb 'List' and resource 'WooCommerce orders', specifies ordering ('newest first') and optional filtering. It distinguishes from sibling tools like 'get_product' (single product) and 'list_products' (products, not orders).

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 usage for listing orders with optional status filter, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it compare with sibling tools. The guidance is implied but not explicit.

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