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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the set of returned customer fields, which is useful for a list tool with no output schema, but says nothing about pagination iteration, result ordering, or the total-count/next_page envelope implied by the page parameter.

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 short sentences, front-loaded with the purpose and the field list. The trailing "GET /v1/customers" is reference detail rather than agent-actionable content, but it costs little.

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 zero-required-parameter list tool with full schema coverage and annotations carrying the safety profile, the description is adequate: it names the resource and the fields returned, partly compensating for the absent output schema. The remaining gap is that the paginated response shape (next_page) is only implied indirectly via the schema's page parameter.

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% — page and limit are both documented in-schema (ranges, defaults, and the "pass the previous reply's next_page" hint). The description adds nothing beyond that, so the baseline of 3 applies.

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?

Uses a specific verb+resource ("List customers") and enumerates the fields surfaced (name, email, phone, company, tax number, country, marketing opt-in), which clearly separates it from create_customer/update_customer. It does not explicitly state how it differs from shoprocket_get_customer (single-record lookup), so sibling differentiation is implied rather than stated.

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 versus shoprocket_get_customer or the other list_* tools, and no prerequisites or exclusions. The only usage-adjacent content is the endpoint reference "GET /v1/customers", which is not a usage instruction.

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