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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds useful behavioral context that the returned records are complete (include SyncToken), but says nothing about page/truncation behavior or latency, which live only in the schema.

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 tight clauses, front-loaded with the core action and followed by the practical payoff (no follow-up get) and the batch-read tip. No filler, though the second clause is slightly compressed in phrasing.

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 read-only search tool with no output schema and full schema coverage, the description supplies the key missing context an agent needs: that results are complete records, so an agent won't waste a call on get_vendor. Return-shape and paging details are adequately handled by the schema.

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 the criteria operators, paging and inactive-record handling are fully documented in the schema. The description's 'Id IN' hint merely echoes an operator already defined there, so baseline 3 is appropriate.

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 vendor records in QuickBooks Online') and implicitly distinguishes itself from the many sibling get_/search_ tools by noting results are full records so 'no get is needed after.' The differentiation is present but indirect rather than naming get_vendor explicitly.

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?

It hints at when to prefer this over a get ('no get is needed after') and shows a batch-read pattern ('read several known Ids in one search with Id IN'), but it never names an alternative tool or states a clear when-not. Usage is implied rather than spelled out.

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