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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so 'read-only, runs straight away' is largely redundant but confirms no confirmation step. The description adds genuine behavior beyond annotations: newest-first ordering, the returned envelope, and the pagination termination rule.

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?

Front-loaded with purpose and return shape, then pagination, then filters — a logical order with little waste. Minor noise: '(site: demo.royalplugins.com)' duplicates the site_id enum description and the read-only clause duplicates annotations.

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 exists, and the description compensates by naming the returned keys and explaining how to page through results. Combined with 100% schema coverage, an agent has everything needed to call it correctly without guessing.

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 100%, so every parameter is already documented in the schema, including after/before inclusivity and site timezone. The description's filter sentence largely restates the schema rather than adding new semantics, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get WooCommerce orders') plus the ordering ('newest first'), which is more than a name restatement. It does not explicitly separate itself from siblings like wc_get_order (singular) or wc_get_products, leaving the agent to infer list-vs-single from naming.

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?

Gives concrete operating guidance: iterate page until page >= total_pages, and filter by creation date via after/before. It stops short of saying when not to use it or naming an alternative tool (e.g. wc_get_order for a single order).

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