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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them ('It does not move money'). Beyond annotations it adds real value: results are full records carrying SyncToken, so a follow-up get is unnecessary. It omits pagination/limit behavior, which the schema covers, so 4 is fair.

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?

Three short sentences, front-loaded with what the tool searches for, then the domain clarification, then the practical retrieval tip. No sentence is 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?

For a read-only search tool with no output schema and 100% schema coverage, the description covers domain semantics and the key return property (full records with SyncToken). It does not need to explain return values, and the remaining detail lives in the schema, so it is complete enough.

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 coverage is 100%, so both parameters are fully documented in the schema. The description adds only a small hint about using Id IN to batch-read known records, which the schema already alludes to via the IN operator. Baseline 3 is appropriate 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?

Specific verb (search) plus resource (credit card payment txn records in QuickBooks Online) and a domain gloss that distinguishes it from lookalike siblings: 'An accounting record of a bank payment toward a credit card balance. It does not move money.' An agent can separate this from search_payments and search_bill_payments without opening any 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 operational guidance ('no get is needed after', 'read several known Ids in one search with Id IN') but never states when to prefer this tool over sibling search tools like search_payments. Usage is implied rather than contrasted with alternatives.

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