List 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 fully covered without the description. The only added behavior is 'paginated', which merely restates what the page/per_page parameters already imply; no mention of filter behavior, default page size, or result contents.

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?

A single short sentence with zero waste and the core action front-loaded. It is efficient, though the brevity comes at the cost of substance rather than being a virtue in itself.

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 six-parameter listing tool with rich filtering semantics (relationship includes, account scoping, store filtering) and no output schema, the description is far too thin. It never explains how the optional filters compose or what a caller should expect from the response, leaving the agent to reconstruct usage entirely from sibling names and the schema.

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 83%, so the schema already documents email, account, include, per_page, and store_id with meaningful detail. The description adds nothing about any of the six parameters, which is acceptable only because the schema does the heavy lifting.

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 ('Retrieves a paginated list of all customers'), which is clear. However, it offers no differentiation from siblings like get_customer, create_customer, or update_customer, so an agent must infer from names alone that this is the bulk-read variant.

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 on when to use this tool versus get_customer or create_customer, nor any mention of prerequisites or exclusions. The word 'paginated' hints at large result sets but the description never says so explicitly.

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