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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the return payload is a full record including SyncToken, so no subsequent get is needed. Pagination/limit behavior lives in the schema rather than here.

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 sentences, front-loaded with the verb+resource and immediately followed by the two pieces of value an agent needs (full-record return, batched Id lookup). Zero 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?

No output schema exists, but the description compensates by describing the return shape (full class records with SyncToken) and the batched-read pattern. Combined with the exhaustive criteria schema, an agent has enough to call it correctly; only explicit pagination guidance is left to 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 both parameters are already fully documented in the schema (criteria syntax, operators, pagination, inactive handling). The description only adds one usage hint ('Id IN'), which is marginal over the schema-rich criteria doc, so baseline 3 is correct.

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 class records in QuickBooks Online') and implicitly separates itself from get_class by noting results are full records requiring no follow-up get. The sibling differentiation is present but indirect rather than by name.

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?

Gives clear tactical context: use it to avoid a follow-up get, and use 'Id IN' to read several known Ids in one call. It doesn't explicitly state when to prefer get_class instead, and offers no exclusions, which keeps it short of a 5.

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