List customers

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

Beyond the annotations, the description discloses meaningful behavior: results include both active and inactive customers, ordering is most-recently-updated first, and paging is caller-driven with a clear termination condition. These details go beyond readOnlyHint and idempotentHint and help the agent understand the tool's actual behavior.

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 front-loaded with the core action, followed by usage guidance, behavior, and paging details in a logical order. Every sentence earns its place, and there is no wasted or redundant wording.

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 straightforward paginated list tool, the description covers ordering, filtering alternatives, inclusion of inactive customers, pagination mechanics, and the read-only nature. Combined with the rich schema and annotations, nothing essential is missing for an agent to invoke it correctly.

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?

The input schema already provides full descriptions for both parameters, including ranges, defaults, and paging math. The description adds a helpful cross-parameter framing ('keep requesting pages until fewer than max_results rows are returned'), but most semantic weight is already carried by the schema, so the baseline of 3 is appropriate.

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 ('List customers') and adds distinctive scope: 'most recently updated first, one page at a time.' It also differentiates from siblings by explicitly routing filtered lookups to search_customers, so an agent can tell this tool apart without opening other schemas.

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 context is explicit: use it 'to browse the roster or to find an Id when you have nothing to filter on; prefer search_customers when you do.' It also provides a practical rule for knowing when pagination is complete: keep requesting pages until fewer than max_results rows are returned.

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