gold_list_customers

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

With no annotations, the description carries some burden and does add value: 'GET' indicates a read-only operation, and 'BYOK fail-closed' discloses the authentication/failure behavior. However, it omits pagination behavior, response shape, and how filters affect results.

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 compact and front-loads the core operation and endpoint. The pricing and 'BYOK fail-closed' phrases are terse but add contextual flags without wasting words.

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?

The definition is not complete enough for a tool with 5 optional parameters, no annotations, and no output schema. It provides the endpoint and a fail-closed hint, but leaves parameter semantics, pagination, and return behavior to guesswork.

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%, and the description adds no meaning to any of the five parameters (page, role, email, search, per_page). An agent must infer semantics solely from parameter names.

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 states a specific verb and resource: 'list Woo customers via GET /wp-json/wc/v3/customers'. This clearly differentiates it from sibling tools like gold_list_products and gold_list_orders.

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 guidance about when to use this tool versus alternatives, nor any when-not-to-use conditions. The 'BYOK fail-closed' hint suggests an auth prerequisite but does not explain tool selection relative to other list tools.

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