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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds no behavioral detail beyond 'search', such as pagination, truncation, filtering limitations, or the fact that it returns one page at a time. Since it contributes no extra transparency, a low score is warranted.

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?

The description is one concise sentence with no filler, making it easy to scan. However, its brevity is partly a result of underspecification rather than deliberate economy, so it does not earn a 5.

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 and only a one-sentence description, the agent is not told what the search returns or what a reimburse charge record looks like. The schema's criteria notes are comprehensive, but the description itself adds almost nothing, leaving the definition incomplete for an unfamiliar agent.

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's description is extensive (operators, ANDed filters, field restrictions, paging). The tool description itself mentions no parameters; if there is meaning here, it comes from the schema, so the baseline of 3 applies.

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?

The description states a clear action and resource: it searches reimburse charge records in QuickBooks Online. It is understandable on its own, though it adds little beyond the tool's name and does not explicitly contrast with sibling search tools, 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?

No guidance is given about when to use this tool instead of other search tools, such as search_bills or search_purchases, nor about prerequisites like connected companies. The only usage context is embedded in the schema's criteria description, not in the tool description itself.

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