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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety profile is known. The description adds that results are full records with SyncToken (no get needed) and the 'Id IN' pattern, which is useful behavioral context beyond annotations. It doesn't cover pagination/truncation here, though the schema does.

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 concise sentences, front-loaded with purpose, then a key operational tip. No wasted text.

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?

For a read-only search tool with rich schema documentation and annotations, this is nearly complete. It covers the SyncToken/full-record benefit and multi-Id retrieval. Pagination is left to the schema, which is acceptable.

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 extensively documented in-schema. The description adds the 'Id IN' usage hint for the criteria field, a small value-add. Baseline 3 applies when schema carries the parameter documentation.

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 bill records in QuickBooks Online.' This clearly identifies a query tool for bills, distinguishable from siblings like get_bill or search_invoices. However, it doesn't explicitly state what makes this different from get_bill beyond the full-records note.

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?

Implied usage is to search/filter bill records, and it notes you can read several Ids in one search with 'Id IN' rather than using get repeatedly. But it doesn't state when to use this versus get_bill explicitly, nor when not to use search (e.g., single known record).

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