list_customers

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to mention key behaviors like default pagination values, how filters are applied, whether the 'filters' object is passed through verbatim, or any limits or edge cases. This is a significant gap for a tool with no output schema or safety annotations.

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 sentence that efficiently states the core purpose without filler or redundancy. It is front-loaded with the action and resource, making it easy to parse.

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?

The tool has 6 parameters, a nested object, no annotations, and no output schema. The description does not compensate for the missing annotation and output schema by explaining return values, default behavior, or the semantics of the 'filters' pass-through. This leaves the definition incomplete for a tool of moderate complexity.

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 provides descriptions for all 6 parameters (100% coverage), so the baseline is 3. The description's mention of pagination, search, and filters adds a high-level grouping but no additional detail beyond what the schema already states. The schema does the heavy lifting here.

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's purpose with the specific verb 'List' and the resource 'store customers', while mentioning pagination, search, and filters. This distinguishes it from singular access tools like get_customer and other list tools for different resources.

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 a list operation, but provides no explicit guidance on when to use this tool versus alternatives such as get_customer for a single customer. No exclusions, prerequisites, or alternative scenarios are mentioned, leaving usage to be inferred from the tool name and sibling context.

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