wp_get_order

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

There are no annotations, so the description carries the full burden. 'Get' clearly implies a non-mutating read operation, and the mention of line items and addresses gives some return-content context. However, it does not describe error behavior, permissions, or the full response shape, which would be more important if an output schema were absent.

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, front-loaded sentence with no filler or redundant details. Every word earns its place by conveying the resource, scope, and key 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?

For a simple getter with one well-documented parameter and no output schema, the description covers the key returned content (line items and addresses). It could mention additional order fields or error conditions, but the current description is sufficient for an agent to correctly invoke the tool in most cases.

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?

The schema already provides 100% coverage with a clear 'Order ID' description for the single 'id' parameter. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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?

Description uses a specific verb ('Get'), a clear resource ('full WooCommerce order details'), and explicitly names content ('line items and addresses'). It clearly distinguishes this single-order retrieval tool from siblings like wp_list_orders.

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?

The description makes the retrieval context clear: use this when you need complete details for a specific order, including line items and addresses. It does not explicitly contrast with wp_list_orders or wp_update_order, but the intended use is evident from the wording.

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