WooCommerce: Get customer

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add depth. It does add the returned data categories, which is useful context beyond annotations, but it omits failure behavior for an invalid or deleted customer_id, whether order history is paginated or truncated, and any auth or store-scoping requirements.

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 core action and followed by a return-value summary; nothing is redundant. The "[UNIFIED]" tag is inert noise that consumes attention without informing the agent.

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?

This is a simple two-parameter read with no output schema and read-only annotations, so the description is close to sufficient. The gaps are the completely undocumented `site` and `customer_id` semantics, which matter for correct invocation given that the schema supplies no descriptions at all.

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% for two required parameters, so the description carries the full burden and does not meet it. It never mentions `customer_id` explicitly, nor does it explain what `site` selects (for example, which store in a multi-site setup) or what form either value takes.

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 uses a specific verb and resource ("Get detailed information about a specific WooCommerce customer") and enumerates what is returned (details, billing, shipping, order history), which separates it from list-style siblings. It does not explicitly name a contrasting sibling such as woocommerce_list_customers or woocommerce_get_customer_report, so the differentiation is implicit rather than stated.

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?

Usage is only implied: "a specific customer" signals a single-record lookup rather than a search or listing, and "order history" hints at use cases covered by the report sibling. There is no explicit when-to-use versus when-not-to-use, no prerequisite note, and no routing to an alternative when a customer ID is unknown.

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