woocommerce_update_order_status

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

No annotations are provided, so the description carries full burden. It fails to disclose critical behavioral traits: whether status changes trigger customer emails, affect inventory/stock management, require specific WooCommerce capabilities, or what occurs if an invalid status is provided.

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 brief and front-loaded, but the '[UNIFIED]' prefix is metadata noise that wastes valuable context space without aiding agent comprehension.

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?

Given zero schema coverage, no annotations, and no output schema, the description is insufficient for a state-changing operation. It omits the complete enumeration of valid WooCommerce statuses, return value structure, and error handling behavior.

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?

With 0% schema description coverage, the description partially compensates by listing example status values (pending, processing, completed) but completely omits semantics for 'site' (URL? slug? identifier?) and 'order_id' (WooCommerce order ID format?).

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?

The description clearly states the tool updates WooCommerce order status with specific examples (pending, processing, completed). It effectively distinguishes from sibling tools like woocommerce_update_product or woocommerce_update_customer by specifying 'order status' as the target resource.

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 provides examples of valid status values, giving implied usage context, but lacks explicit guidance on when to use this versus other order operations or prerequisites like order existence checks.

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