WooCommerce: Create order

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

Annotations already disclose readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is known and does not need repeating. What the description should add instead — whether the payment method is actually charged, whether the default 'pending' status has side effects, whether duplicate submissions create duplicate orders — is entirely absent. Given a destructive, non-idempotent mutation, this is a meaningful gap.

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?

Two tight sentences with the verb and resource front-loaded and zero filler. The brevity is appropriate in structure; the problem is under-specification, not verbosity.

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?

Seven parameters at 0% schema coverage, no output schema, and a destructive annotation together set a high bar that the two-sentence description does not meet. An agent cannot determine payload shapes or post-creation behavior from this definition.

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%, so the description carries the full burden, and it only gesture-references 'line items, billing, shipping, and payment method' without any format, structure, or accepted-value detail. Three parameters (site, status, customer_id) are never mentioned at all, and for a payload-oriented tool like this, the expected serialization of billing/shipping/line_items is the single most decision-critical piece of information.

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 and resource ('Create a new WooCommerce order') and enumerates the configurable domains, which cleanly separates it from woocommerce_get_order, woocommerce_list_orders, and woocommerce_update_order_status. It stops short of naming any sibling as a contrast, so it stays at 4 rather than 5.

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?

There is no statement of when to use this versus alternatives, no prerequisites (store connection, valid customer/product references), and no note on what happens after creation (e.g., order status flow). The agent must infer all usage context from the tool name alone.

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