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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds the non-obvious return-completeness trait that records include SyncToken. It does not add auth, rate-limit, or paging behavior (paging lives in the schema), so it is solid but not rich.

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 compact sentences, front-loaded with the action and the differentiator; every clause carries information an agent needs. 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?

With no output schema, the description carries the return-value burden and does so at a high level (full records + SyncToken), which is the key fact. Paging/truncation and company selection are handled in the schema, leaving only minor gaps.

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% and the criteria parameter is documented exhaustively in the schema itself (operators, AND semantics, filterable fields, case sensitivity, 1000-record paging). The description adds no parameter-level meaning beyond that, 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 deposit records in QuickBooks Online') and immediately distinguishes itself from get_deposit by noting results are full records with SyncToken so a follow-up get is unnecessary. An agent can pick this over the ~90 siblings without opening a schema.

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 a concrete usage pattern ('read several known Ids in one search with Id IN') and implies when this replaces get_deposit. It stops short of an explicit when-not-to-use statement (e.g., single known Id or bulk export), so it is clear context rather than full routing guidance.

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