WooCommerce MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a creation tool, implying a mutation, but doesn't specify permissions needed, whether the operation is idempotent, what happens on duplicate emails, or the response format. The mention that 'Only email is required' adds minimal context about input constraints but lacks depth on behavioral traits.

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 two short sentences that are front-loaded: the first states the purpose, and the second adds a key constraint. There is no wasted verbiage, making it efficient and easy to parse.

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 the tool's complexity (a mutation with 4 parameters, no annotations, but an output schema exists), the description is minimally adequate. The output schema likely covers return values, reducing the need for description details there. However, for a creation tool with no annotations, more context on behavior, permissions, or error handling would improve completeness.

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 for undocumented parameters. It adds value by specifying that 'Only email is required,' clarifying the required parameter among the four. However, it doesn't explain the semantics of optional parameters like first_name or username, leaving gaps in understanding their purpose or format.

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 action ('Create a new customer') and specifies the resource ('customer'), which distinguishes it from siblings like create_product or create_order. However, it doesn't explicitly differentiate from other customer-related tools like get_customer or search_customers, though the 'create' verb inherently implies a write operation versus read operations.

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. It doesn't mention prerequisites, such as needing admin permissions or a valid email format, nor does it contrast with sibling tools like search_customers for finding existing customers. The only usage hint is the requirement for email, but this is already covered in the schema.

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