search_customers

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

With no annotations, the description must disclose behavioral traits. It fails to mention that the tool is read-only, returns a list of customers, or explain pagination behavior (even though the schema includes limit/offset). No discussion of performance or side effects.

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, concise and front-loaded. However, it is under-specified, lacking important context. Conciseness at the expense of completeness reduces effectiveness.

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 complexity of the parameters (nested objects, pagination, multiple filter forms) and the absence of annotations and output schema, the description is too brief. It does not explain the advanced filter structure, pagination default, or company targeting, leaving significant gaps.

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?

While the schema covers 50% of parameters with descriptions (e.g., criteria and company), the tool description adds no additional meaning beyond 'match given criteria'. It does not explain the two forms of criteria (advanced vs. legacy) or the purpose of limit/offset/fetchAll, which would help an agent use parameters effectively.

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 verb 'Search' and the resource 'customers in QuickBooks Online', indicating what the tool does. However, it does not differentiate from sibling search tools like search_accounts or search_invoices, which follow the same pattern.

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?

No guidance is provided on when to use this tool versus alternatives, such as get_customer for a single record or other search tools. The description only says 'match given criteria' without any context on prerequisites or exclusions.

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