woocommerce_update_customer

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 but fails to specify mutation semantics (PATCH vs PUT), what happens when customer_id is invalid, or whether the operation is idempotent. It states 'Update' implying mutation but lacks safety/destructive context.

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 with the primary action front-loaded. The '[UNIFIED]' prefix is metadata cruft that adds no value for the agent. Otherwise efficient with no redundant phrases.

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 7-parameter mutation tool with 0% schema coverage and no output schema, the description is insufficient. Critical gaps remain around the 'site' identifier, complex field formats (billing/shipping as strings), error handling, and return value structure.

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 coverage is 0%, requiring the description to compensate. It enumerates updatable fields (name, email, billing, shipping) mapping to 5 of 7 parameters, but fails to explain the 'site' parameter (domain? ID?) or the expected format for 'billing' and 'shipping' (JSON string? Address structure?). Baseline 3 for field enumeration with incomplete compensation for zero schema coverage.

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 (Update), resource (WooCommerce customer), and specific fields that can be modified (name, email, billing, shipping). It distinguishes from 'create' operations by specifying 'existing' customer, though it doesn't explicitly name sibling tools like woocommerce_create_customer.

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 on when to use this tool versus alternatives like woocommerce_create_customer or woocommerce_get_customer. There are no prerequisites mentioned (e.g., needing a valid customer_id) or warnings about partial vs full updates.

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