woocommerce_create_customer

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

No annotations provided, so description carries full burden. States the write operation ('Create') but lacks disclosure of idempotency, conflict handling (duplicate emails), return values, or required permissions. Fails to compensate for missing safety annotations.

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?

Single sentence structure is efficient, but the '[UNIFIED]' prefix wastes valuable front-loaded space without adding semantic value. Otherwise appropriately sized for the parameter count.

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 creation tool with no output schema and no annotations, the description omits critical context: what object is returned on success (customer ID? full object?), error conditions (duplicate email handling), and whether the operation is atomic.

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?

With 0% schema description coverage, the description lists available parameters (email, name, username, password, billing, shipping) and indicates optionality. However, it doesn't explain data formats—particularly for 'billing' and 'shipping' which are complex address objects typed as strings in the schema.

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 'Create a new WooCommerce customer' with clear verb and resource. Distinguishes from siblings like woocommerce_update_customer and woocommerce_get_customer through the explicit 'Create' operation. The '[UNIFIED]' prefix is noise but doesn't obscure the core purpose.

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?

Provides no guidance on when to use this versus woocommerce_update_customer or when the customer already exists. Only indicates parameter requirements ('Requires email...'), lacking workflow context or error scenarios.

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