getCustomers

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

Annotations indicate non-destructive, idempotent, read-only behavior. The description adds behavioral details like the inclusion of both member and non-member customers, filterable by the 'member' parameter, and search capabilities. No contradictions.

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 paragraph but efficiently front-loads the main purpose and then lists capabilities. Each sentence adds necessary information, with no redundancy.

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?

Given the tool's complexity (16 parameters, no output schema), the description covers pagination, filtering options, and sibling references. It is sufficiently complete for an AI agent to understand usage, though it omits return format details.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the member filter, pagination defaults (limit default 10, max 100), and the types of searches (partial match, exact match).

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 it retrieves a list of customers, including both member and guest customers, with extensive filtering options. It explicitly distinguishes from sibling tools like getCustomer, postCustomers, and updateCustomers.

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 provides explicit guidance on when to use this tool (listing with filters) and when to use alternatives (single customer: getCustomer, new registration: postCustomers, update: updateCustomers). It also explains pagination with limit and offset.

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