List customers

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

Annotations already declare readOnlyHint=true, so the description adds minimal behavioral context beyond 'paginated'. Pagination behavior is also documented in the schema parameters, so the description does not significantly disclose additional traits like default limits, auto-pagination semantics, or response envelope structure.

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 a single, front-loaded sentence with no filler. 'List customers of the store (paginated)' is concise and every word adds value: verb, resource, scope, and behavior.

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?

While the schema and annotations cover safety and pagination parameters, the description does not clarify the response structure (e.g., whether it returns a raw array or a paginated wrapper object). With no output schema, this is a gap. However, the simplicity of the tool and good schema coverage keep it from being incomplete.

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%, with each parameter (all, page, per_page) having clear descriptions. The tool description adds no extra meaning beyond the term 'paginated', which is already inferred from the schema. Baseline 3 is appropriate given the schema fully documents parameters.

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 clearly states the tool lists customers of the store, with a specific verb ('list') and resource ('customers'). It distinguishes from sibling tools like get_customer (single) and update_customer (modification) by indicating a collection retrieval operation.

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 implies usage for fetching a paginated list of all customers but does not explicitly state when to use it versus alternatives (e.g., get_customer for a single customer, get_customer_orders for a specific customer's orders). No exclusions or when-not-to-use guidance is provided.

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