list_customers

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The term 'Search' implies a read-only operation, but it does not explicitly state idempotency, side effects, authentication requirements, or pagination behavior. This is adequate but not fully transparent.

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 conveys the tool's purpose and usage pattern. It includes the endpoint in parentheses for context without any superfluous 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 12 optional parameters, no output schema, and no annotations, the description is minimal. It lacks details about result format, pagination, rate limits, or other typical behaviors for a search tool. The description does not fully equip an AI agent to use the tool effectively.

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?

With schema description coverage at only 17% (2 out of 12 parameters have descriptions), the description should compensate but only adds a general statement about optional filtering. It does not elaborate on the meaning or format of individual parameters beyond what the schema provides.

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 'Search the Diaspark customer list', identifying the verb (search) and resource (customer list). It also includes the specific endpoint for reference. The siblings are inventory_search and sales_history_report, so this tool is distinct in its purpose.

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 explicitly states 'All fields are optional filters; leave a field out to not filter on it', providing clear guidance on how to use the parameters. Although it doesn't discuss when not to use the tool or compare to siblings, the optional filter behavior is well-explained.

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