woocommerce_create_order

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to mention critical side effects such as inventory reduction, email notifications to customers, or payment processing implications. It does not disclose idempotency, error behaviors, 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 is appropriately brief with two sentences and front-loaded action verb. However, the '[UNIFIED]' prefix adds noise without providing actionable context, slightly reducing an otherwise efficient structure.

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 7 parameters with 0% schema coverage, no annotations, and no output schema, the description is insufficient. It lacks return value documentation, error case handling, data format specifications for complex fields, and authentication/permission requirements necessary for a commerce transaction creation tool.

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 mentions line_items, billing, shipping, and payment_method, it omits the required 'site' parameter and does not explain that complex objects (billing/shipping) must likely be serialized as JSON strings given the schema types, nor does it document the 'status' default value of 'pending'.

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 specific action ('Create a new') and resource ('WooCommerce order'), distinguishing it from siblings like woocommerce_delete_order, woocommerce_get_order, and woocommerce_update_order_status. The mention of 'line items, billing, shipping, and payment method configuration' clarifies the scope of the creation operation.

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 lists supported features but provides no guidance on when to use this tool versus alternatives (e.g., when to use woocommerce_update_order_status instead), nor does it mention prerequisites such as existing customer or product requirements before order creation.

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