woo_get_order

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

With no annotations provided, the description carries the full behavioral burden and delivers almost nothing: it doesn't say whether the call is read-only (implied by 'Get'), what happens on an invalid/missing order id, whether authentication scoping applies, or what the response contains. 'Details' is undefined.

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?

A single front-loaded sentence with no filler, which is good, but it is also under-specified rather than tight – there is no second sentence to earn the brevity. Adequate but minimal.

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 tool with no annotations and no output schema, the description should at least sketch what 'details' are returned or how errors are surfaced. Instead it leaves the agent to call blind, which is a meaningful gap against the complexity of an order entity.

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 100% – both 'id' (Order ID) and 'site' (Site id, see list_sites) are documented in the schema. The description adds no syntax, format, or cross-parameter meaning, so the baseline 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 ('Get') and resource ('WooCommerce order details'), so the agent knows it retrieves a single order. It doesn't explicitly distinguish itself from nearby siblings like woo_list_orders or woo_get_order_notes, but the singular 'order' plus the id parameter makes the intent reasonably clear.

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?

No guidance on when to use this versus woo_list_orders (for browsing), woo_get_order_notes (for notes), or woo_update_order_status. No prerequisites or context conditions are stated; the agent must infer usage entirely from the name.

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