Read an order

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

Annotations already cover readOnly/idempotent/destructive, so the description adds real context beyond them: 'needs manage_woocommerce', 'Requires WooCommerce', and the precise not-found error behavior on an unknown id. Doesn't mention rate limits or caching, but adds meaningful operational constraints.

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?

Three dense sentences: purpose first, return shape second, failure/permission constraints last. No output schema exists, so enumerating the returned fields earns its space rather than being filler.

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 compensates by listing returned fields (id, status, total, currency, customer, email, date, items, payment_method, note_to_customer), plus permissions and error semantics. An agent has everything needed to call and interpret it correctly.

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?

Single parameter with 100% schema coverage; the schema already explains that the id is the WooCommerce-displayed order number unless renumbered by a plugin. The description only restates 'by id', so it adds nothing beyond the schema — baseline 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?

States a specific verb and resource ('get one order by id') and explicitly distinguishes itself from the sibling that lists many orders. An agent can tell it apart from wp_wc_list_orders without opening a schema.

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?

Names the alternative (wp_wc_list_orders) and the condition that routes there — need to discover ids first. Also notes the not-found failure on unknown ids. No explicit 'do not use when' exclusion, but the routing guidance is concrete.

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