WooCommerce MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Create an order' which implies a write/mutation operation, but doesn't mention permissions required, whether this triggers payment processing, what happens on failure, or what the response contains. The example helps but doesn't cover behavioral aspects like side effects or error conditions.

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 extremely concise with only two sentences, both essential. The first states the purpose, the second provides critical format information for the most complex parameter. No wasted words or redundant information.

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 8 parameters, 0% schema description coverage, and no annotations, the description is insufficient. While an output schema exists (which helps), the description doesn't explain what happens when creating an order, what validation occurs, or how to handle the many undocumented parameters. It leaves too much unexplained for proper agent usage.

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 must compensate. It only provides semantics for one parameter ('line_items') with an example format, leaving 7 other parameters (customer_id, status, billing_email, etc.) completely unexplained. The description adds value for line_items but fails to address the majority of parameters.

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 verb ('Create') and resource ('order'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'create_customer' or 'create_product' beyond the resource name, nor does it specify what type of order (e-commerce, service, etc.).

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?

No guidance is provided about when to use this tool versus alternatives like 'update_order_status' or 'get_order'. The description doesn't mention prerequisites (e.g., needing existing products/customers), nor does it specify when this tool is appropriate versus other creation tools in the sibling list.

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