woocommerce_delete_order

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

With no annotations provided, the description carries the full burden. It discloses the behavioral difference between trashing (recoverable) and permanent deletion, but omits critical safety details like whether this affects inventory levels, payment refunds, or required permissions.

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 wastes front-loaded space with the '[UNIFIED]' metadata tag, which provides no value to the agent. Excluding that tag, the two sentences are appropriately concise, though the prefix reduces clarity.

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 destructive operation with 0% schema coverage and no output schema, the description is insufficient. It lacks return value information, error conditions, side effects (inventory restoration), and safety warnings that are essential for irreversible operations.

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%, requiring the description to compensate. While it implicitly explains the 'force' parameter through the 'permanently delete' vs 'trash' distinction, it completely fails to document 'site' (WooCommerce site identifier) or 'order_id' semantics.

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 deletes or trashes WooCommerce orders, distinguishing it from siblings like woocommerce_update_order_status (which only changes status) and woocommerce_get_order. It specifies the resource (order) and the dual modes (delete vs trash).

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 explains the two modes (permanent delete vs trash) but lacks explicit guidance on when to use each, prerequisites (e.g., order state requirements), or when to prefer cancellation via update_order_status instead of deletion.

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