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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the safety profile is covered. The description adds useful behavioral detail about the return payload (full records with SyncToken, no get needed) plus the batch-read pattern. However, with the criteria schema carrying pagination and truncation behavior, the description itself contributes only modestly beyond structured data.

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 with no filler, and the primary purpose is front-loaded before the workflow tips. Every clause earns its place.

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 that results are full records containing SyncToken, which tells the agent what comes back. Combined with the schema's coverage of filtering, pagination and inactive-record behavior, an agent has what it needs; only the overlap with get_account_list is left unexplained.

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 'company' and the extremely detailed 'criteria' parameter are already fully documented in the schema. The description adds only the 'Id IN' usage hint for criteria, which is a marginal gain over the schema's own operator list. Baseline 3 applies when the 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 and resource ('Search account records in QuickBooks Online') that separates it from the many other search_* siblings by resource. It does not, however, differentiate itself from the closely overlapping get_account and get_account_list siblings, so an agent still has to guess which account-read tool to pick.

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 concrete context: results are full records so no follow-up get is required, and several known Ids can be read at once via 'Id IN'. That is an actionable usage recipe, but it never names an alternative tool or states an exclusion (e.g. when to prefer get_account_list).

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