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

With readOnlyHint and destructiveHint already covering the safety profile, the description still adds real value: it discloses that returns are full records including SyncToken, and that Id IN allows multi-record reads in one call. It omits pagination/truncation behavior, but that is documented in the criteria 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 short sentences, front-loaded with the purpose and immediately followed by the two facts that change how an agent calls it. No filler.

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?

There is no output schema, and the description compensates by stating the shape of results (full records with SyncToken). Combined with a fully documented criteria schema and read-only annotations, an agent has nearly everything needed; only pagination limits live solely in 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 coverage is 100% and the criteria field description is unusually detailed (operators, AND-only filtering, field names, 1000-record page cap). The description's only added parameter guidance is the 'Id IN' batching pattern, which the schema already lists as a supported operator, so the baseline of 3 applies.

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 specific verb and resource ('Search exchange rate records in QuickBooks Online'), which is enough to separate it from update_exchange_rate and delete-style siblings. It stops short of explicitly distinguishing itself from get_exchange_rate, though the 'no get is needed after' line implies the split.

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?

Usage is implied rather than stated: full records mean a follow-up get is unnecessary, and Id IN lets you batch known Ids. There is no explicit statement of when to prefer this over get_exchange_rate, and no exclusions, so guidance is only partial.

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