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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description still adds useful behavioral context: it is LIVE, returns no personal data, and revenue excludes cancelled/refunded/failed orders.

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 a single dense sentence with no wasted words, and the key safety qualifier 'READ-ONLY, LIVE' is front-loaded. The parenthetical field list is compact and earns its place by clarifying the return contents.

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?

With no output schema, the description appropriately lists the returned order fields and explains the revenue exclusion rule. It is nearly complete for a read-only listing tool, though it does not explain how store_id should be sourced or whether results are paginated beyond the schema's limit parameter.

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 coverage is 75%, so three of four parameters are described in the schema and the description does not need to carry them. The description adds no parameter-level meaning, and store_id is undocumented in both schema and description, leaving a small 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 states a specific verb and resource: listing recent WooCommerce orders, and it adds that revenue by currency is included. The WooCommerce scope distinguishes it from generic order tools like get_orders, though it does not explicitly name an alternative sibling.

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?

Usage is implied by 'Recent WooCommerce orders' and 'plus revenue by currency', suggesting this is for current order listing and currency-level revenue snapshots. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative such as woo_hub_query or get_orders.

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