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

The top-level description adds no behavioral detail beyond the annotations; it only restates the operation. It does not mention filtering semantics, pagination, truncation, or unavailable sensitive fields, which are documented only in the schema. No contradiction with readOnlyHint=true/destructiveHint=false exists.

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?

Single sentence, no filler, and the core purpose is stated immediately. The brevity is appropriate given the heavy lifting done by the schema.

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?

Together with the rich criteria parameter documentation, the tool definition covers filters, AND semantics, unsupported fields, case sensitivity, pagination, and default behavior. The absence of an output schema and the terse top description leave the exact return shape implied rather than stated, so it is not a 5.

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 schema already documents both parameters thoroughly (100% coverage), including the full criteria grammar and operators. The description itself adds no parameter-level detail, so it sits at the baseline 3.

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 names a concrete operation and object: 'Search estimate records in QuickBooks Online.' It is clear enough to distinguish from create/update/delete_estimate and from the singular get_estimate, although it does not explicitly contrast with sibling tools.

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 gives no guidance on when to choose search_estimates versus get_estimate or other search tools. The only behavioral hint, 'Omit to return the first page of all estimate records,' lives in the schema's criteria parameter, not in the description, and there is no explicit 'use this when...' statement.

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