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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world). The description adds value on top of them by disclosing the return shape (full records including SyncToken), which matters because there is no output schema, and by implying a batch-read capability. Pagination behavior is left to 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 sentences, zero waste, front-loaded with the purpose. The batching/return-shape tips are compact and each 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?

With no output schema, the description usefully signals what a result contains (full records with SyncToken). Combined with the exhaustive criteria schema, an agent has enough to call it correctly; only pagination specifics are absent, and those live 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 description coverage is 100% and the criteria description is exceptionally rich (operators, AND-only semantics, case sensitivity, field limits, 1000-record paging), so the schema carries the burden. The description only adds the "Id IN" batching hint, which is a marginal supplement to an already complete schema.

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 tax rate records in QuickBooks Online") and implicitly distinguishes itself from get_tax_rate by noting results are full records with SyncToken. It doesn't explicitly name the sibling tools it competes with, so it falls short of a 5.

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 usage direction: prefer this over a follow-up get because records are complete, and batch known Ids with "Id IN". It stops short of stating when-not-to-use or explicitly naming alternatives like get_tax_rate, 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.