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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds the underlying GET endpoint, but says nothing beyond what the schema implies about pagination iteration across pages or result volume.

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 compact sentences with the resource definition front-loaded and the endpoint trailing as supporting detail. Nothing is redundant or padded.

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 simple zero-required-parameter list endpoint with full schema documentation and annotations covering the safety profile, the description is sufficient to invoke the tool. The only gap is lack of explicit routing relative to get_customer, which is a minor omission rather than a blocker.

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 rql, sort, pgnum and pgsiz each documented including examples and defaults, so the schema carries parameter semantics fully. The description contributes no additional parameter guidance, which is acceptable at this coverage but is the baseline, not added value.

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 (customers), and disambiguates the domain term with a parenthetical ('the companies whose goods it stores') plus the backing endpoint GET /customers. It reads clearly against the singular sibling extensiv_get_customer, though it never names that sibling explicitly.

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?

Usage is only implied: a plural 'list' tool contrasted with get_customer suggests bulk enumeration versus single-record lookup, but the description never states when to use this over extensiv_get_customer or that ids returned here feed that tool. No exclusions or prerequisites are given.

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