woocommerce_get_customer

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

No annotations are provided, so the description carries full burden. It successfully discloses the return value structure ('Returns customer details, billing, shipping, and order history'), which is critical behavioral information for a read operation. It does not mention rate limits or auth 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?

The description is two sentences with clear structure: purpose first, return value second. The '[UNIFIED]' prefix is minor metadata noise but does not significantly detract from the overall efficiency. No redundant or tautological language.

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 simple 2-parameter read tool without output schema, the description adequately covers the return data structure. However, given 0% schema coverage, it should have explicitly documented both the 'site' and 'customer_id' parameters to be fully complete.

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 must compensate but fails to fully do so. While 'specific' implies the customer_id parameter, there is no explanation of the 'site' parameter (what format, what it represents) or explicit confirmation that customer_id is an integer.

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 specific action ('Get') and resource ('detailed information about a specific WooCommerce customer'), distinguishing it from sibling tools like woocommerce_list_customers (plural/list) and woocommerce_create/update_customer (mutations). The scope is precisely defined.

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 term 'specific' implies usage when a customer_id is available, but there is no explicit guidance on when to use this versus woocommerce_list_customers for searching, or prerequisites like needing a valid customer_id. Usage is implied rather than stated.

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