woocommerce_list_customers

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

No annotations are provided, so the description carries the full burden. It discloses that results are paginated and specifies which fields are returned (email, orders count, total spent). However, it omits safety information (read-only nature), authentication requirements, rate limits, or error behaviors.

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 efficiently structured in two sentences with the action front-loaded. The '[UNIFIED]' prefix appears to be metadata noise without explanation, slightly detracting from an otherwise compact description.

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?

Given 0% schema coverage, no annotations, and no output schema, the description provides minimal viable context for a 6-parameter tool. While it explains what the tool does, the lack of parameter documentation and usage guidance leaves significant gaps for correct invocation.

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%, requiring the description to compensate, but it fails to document any of the 6 parameters. Critical parameters like 'site' (required, format unclear) and 'role' (possible values unknown) receive no explanation, leaving significant semantic gaps.

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 tool 'List WooCommerce customers' with specific verb and resource. It distinguishes this as a bulk list operation by mentioning 'paginated customer list' and specific returned fields (email, orders count, total spent), implying it retrieves multiple records rather than a single 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 explicit guidance on when to use this versus siblings like 'woocommerce_get_customer' (single retrieval) or 'woocommerce_create_customer'. No mention of prerequisites, permissions, or filtering strategies using the available parameters.

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