woo_customers

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It merely says 'list', implying a read-only operation, but omits any details about side effects, rate limits, data volume, or return format.

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 extremely concise but at the expense of being under-specified. It fails to provide essential information, making it ineffective for an AI agent to correctly select and invoke the tool.

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 the tool has 10 parameters, no output schema, and no sibling differentiation, the description is woefully incomplete. It lacks any context that would help an agent understand its capabilities or constraints.

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 and 10 parameters, the description adds no meaning to any input schema field. It does not explain the role of required fields (store_url, consumer_key, consumer_secret) or optional filters like per_page, page, search, email, role, orderby, and order.

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 'List WooCommerce customers' is a tautology, essentially restating the tool name without providing any specific verb+resource differentiation. It fails to distinguish from sibling tools like woo_orders or woo_products.

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 given on when to use this tool over alternatives. There is no mention of authentication prerequisites, pagination, or any context for usage.

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