wordpress_wc_update_order_status

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't state what permissions are required, whether the change is reversible, what happens if the order doesn't exist, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the core purpose immediately. Every word earns its place in conveying the essential function.

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 mutation tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain parameter meanings, behavioral implications, or expected outcomes. The context signals indicate high complexity (mutation operation) but the description provides minimal support for agent understanding.

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 description mentions 'order status' which relates to the 'status' parameter, but doesn't explain what 'orderId' refers to or provide any details about valid status values (e.g., 'processing', 'completed'). With 0% schema description coverage and 2 undocumented parameters, the description adds minimal value beyond what's implied by the tool name.

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 'Update WooCommerce order status' clearly states the verb ('update') and resource ('WooCommerce order status'), making the purpose immediately understandable. It distinguishes this tool from general WordPress update tools by specifying the WooCommerce context, though it doesn't explicitly differentiate from other WooCommerce tools like 'wordpress_wc_update_product' or 'wordpress_wc_update_stock'.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing order), when not to use it (e.g., for creating orders), or how it relates to sibling tools like 'wordpress_wc_get_orders' or 'wordpress_update_post'. Usage is implied only by the tool name and description.

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