woo_customers

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description merely restates that this is a list operation and adds no context about pagination, filtering behavior, authentication requirements, rate limits, or return shape.

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 definition is a single front-loaded sentence with no wasted words, but it is severely under-specified for a 10-parameter authenticated tool. This is terseness rather than appropriately sized conciseness.

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 10-parameter WooCommerce customer endpoint with no output schema and no parameter descriptions, one sentence is inadequate. The agent is missing essential information about filtering, pagination, and authentication behavior.

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?

There are 10 parameters with 0% schema description coverage, and the description mentions none of them. It says nothing about pagination, role filtering, email lookup, search, ordering, per_page, or the required store_url/consumer_key/consumer_secret credentials, so it does not compensate for the schema gap.

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?

States a specific verb ('List') and resource ('WooCommerce customers'), so the basic operation is clear. However, it gives no differentiation from sibling customer-listing tools such as shopify_customers, square_customers, or quickbooks_customers.

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 description provides no when-to-use guidance, prerequisites, or alternatives. An agent must infer from the name alone that this is the WooCommerce-specific customer list operation.

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