list_customers

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

Annotations already declare readOnlyHint=true, so the safety of the operation is clear. The description adds value by describing the return format and the effect of the detail parameter, but does not disclose additional behaviors like pagination limits or rate limits.

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 sentences efficiently convey purpose, filters, and return format. No wasted words or repetition of schema. Front-loaded with key information.

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 9 parameters and no output schema, the description covers the main intent and partial return format. However, it omits details on pagination structure (page/limit) and the raw parameter, leaving some gaps for an agent to infer from the schema alone.

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%, but the description adds specific meaning beyond the schema by detailing what fields are included in summary vs full detail. For example, 'summary: {id, name, email, phone, ordersCount, totalSpent}' and 'full adds address/externalId/all phones' provides concrete context that the schema's generic 'compact' vs 'full' description lacks.

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/searches customers by specific fields (name, email, phone, created-date) and describes the return format. It uses specific verb+resource, and the resource 'customers' distinguishes it from sibling tools like list_products or list_orders.

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 listing or filtering customers but does not explicitly discuss when to use this tool versus alternatives like get_customer (single) or create_customer. 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.