WooCommerce MCP Server

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. It states 'Create a product' which implies a write operation, but doesn't mention authentication requirements, rate limits, side effects, or what happens on success/failure. The description lacks crucial behavioral context for a mutation tool.

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 brief and to the point with two sentences. It efficiently communicates the core action and key parameters. While it could be more comprehensive, there's no wasted verbiage or unnecessary repetition.

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 10 parameters, 0% schema description coverage, and no annotations, the description is insufficient. It doesn't explain the return values (though an output schema exists), doesn't cover most parameters, and provides minimal behavioral context. Given the complexity and lack of structured documentation, this description leaves too many gaps.

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 schema provides no parameter descriptions. The description mentions 'Type: simple, grouped, external, variable' and 'Categories: comma-separated IDs' which partially explains two parameters (product_type and categories). However, 8 other parameters remain completely undocumented in both schema and description, leaving significant gaps.

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 'product', making the purpose evident. It also specifies product types and categories, which helps distinguish it from other creation tools like create_coupon or create_customer. However, it doesn't explicitly differentiate from update_product or delete_product in terms of when to use each.

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 like update_product or delete_product. It mentions product types and categories but doesn't explain when to choose one type over another or what prerequisites might be needed. No explicit when/when-not statements are present.

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