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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational context — that it uses local WordPress authentication and needs no WooCommerce REST API keys — but says nothing about result ordering, total counts, or how filters combine.

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?

Two sentences, front-loaded with the core action, then the authentication note. No filler, though the 'Mirrors woocommerce-mcp-server method get_customers' clause is implementation trivia with limited value to an agent.

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 paginated list tool with fully documented parameters and no output schema, the definition covers what it does, auth model, and paging/filtering capability. The one real gap is the open-ended `filters` object — valid filter keys (email, role, search, etc.) are never hinted at, leaving the agent to guess.

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 100%, including explicit site_id guidance to call list_sites first and perPage bounds, so the schema carries parameter meaning. The description adds nothing beyond that, which is the expected baseline when coverage is complete.

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 and resource: 'Retrieves WooCommerce customers' with pagination and filters. The plural form implicitly contrasts with the singular wc_get_customer sibling, but the description never names that alternative to make the distinction explicit.

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 when-to-use guidance: nothing says to use this for browsing/listing versus wc_get_customer for single lookups, nor which filters to apply for common cases. Usage is only inferred from the words 'pagination and filters'.

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