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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that full records with SyncToken are returned and that Id IN can batch reads, which is useful behavioral context. However, it doesn't mention pagination limits (though schema covers that) or rate limiting. A 3 is appropriate given some added value beyond 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?

Two short sentences, front-loaded with the core purpose and then the key usage tip. No wasted words.

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?

For a readOnly search tool with no output schema, the description covers the essentials: what it searches, that full records are returned, and a batching tip. The schema covers parameters and pagination, so the description needn't repeat those. Slightly incomplete on when to use this vs get_estimate, but overall adequate.

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 description coverage is 100%, so parameter details are fully documented in the schema. The description mentions the Id IN operator which is an example of criteria usage, adding minor value. Baseline 3 is correct when schema does the heavy lifting.

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?

States a specific verb+resource: search estimate records in QuickBooks Online. It's clearly distinguished from get_estimate implicitly by being a search, though it doesn't explicitly name the alternative.

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?

Adds a concrete usage tip: results are full records so no get is needed after, and you can read several known Ids in one search with Id IN. This gives practical usage context but doesn't explain when to prefer this over get_estimate or other search tools explicitly.

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