WooCommerce: Get order

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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally. The description adds value by enumerating the returned payload (line items, totals, billing, shipping), which tells the agent what data becomes available. It stops short of error behavior for a nonexistent order or per-site auth requirements.

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?

Two short sentences, front-loaded with the core action and followed by return contents; nothing is redundant. The "[UNIFIED]" prefix is token noise that does not earn its place, and the second sentence partly restates the first.

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?

For a simple two-parameter read with annotations and no output schema, the return-value summary is adequate and saves an output schema. However, the completely undocumented "site" parameter leaves the definition incomplete for correct invocation, which matters more here than return-field detail.

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 description coverage is 0%, so both parameters rest entirely on the description, and it says nothing about them. "site" is especially ambiguous – it could be a store URL, an alias, or an ID – and "order_id" format is never clarified. The sentence about return contents does not compensate for this 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?

States a specific verb and resource: "Get detailed information about a specific WooCommerce order," so the agent knows this is a single-record read. It does not distinguish itself from woocommerce_list_orders or explain how an order_id is obtained, so sibling differentiation is only implicit in the singular "order".

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 "a specific order" – use it when you already have an order identifier. No explicit when-not, no mention that list_orders should be used to discover order IDs, and no prerequisites such as the order existing or the site being configured.

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