WooCommerce: Create customer

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds the required/optional split, but leaves the most consequential behavior unstated: since idempotentHint is false, an agent needs to know whether a duplicate email errors out, and whether the customer is emailed credentials when password is supplied.

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?

Two sentences, front-loaded with the action and followed by the required field, with no filler. The '[UNIFIED]' prefix and 'optionally includes' phrasing consume space without adding decision value.

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 an 8-parameter, non-idempotent create mutation with zero schema description coverage and no output schema, the definition is thin: it never explains the site parameter's role, the serialization expected for billing/shipping, duplicate-email handling, or what the call returns (e.g. the new customer ID).

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 has to carry parameter meaning; it names email, name, username, password, billing and shipping, which helps mapping, but adds no format guidance. This matters most for billing and shipping, which are typed as plain nullable strings in the schema and are almost certainly expected as serialized address objects/JSON — the description gives no hint.

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 a specific verb and resource ('Create a new WooCommerce customer') and separates required from optional inputs, so it is distinguishable from update_customer/delete_customer by name alone. It does not explicitly contrast itself with the sibling write tools, which keeps it below a 5.

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?

There is no when-to-use guidance at all: nothing tells the agent to prefer this over woocommerce_update_customer when the email already exists, or to check woocommerce_list_customers first. The only routing signal is the implicit 'Create' in the name.

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