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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description only restates the read/search behavior without adding useful context such as pagination, result truncation, filtering constraints, or return behavior. The detailed behavioral notes live inside the schema, not the top-level description, so the description itself adds little beyond the annotations.

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 a single, front-loaded sentence with no filler: it names the action, resource, and platform. It is concise, though it is closer to under-specification than to rich but efficient guidance.

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?

The tool is a simple read-only search with no required parameters, and the criteria schema provides substantial operational guidance about filtering, pagination, and truncation. However, there is no output schema and no explicit mention of the return shape, so the description alone is not fully complete for an agent trying to predict the result.

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?

Both parameters have complete schema descriptions (100% coverage), including the detailed criteria description covering operators, AND semantics, field limitations, pagination, and truncation. The top-level description adds no parameter-level meaning, so the baseline score of 3 is appropriate.

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 verb ('Search'), a specific resource ('exchange rate records'), and the platform ('QuickBooks Online'), so an agent can tell this is a query/list operation. It does not explicitly distinguish itself from the sibling get_exchange_rate, but the verb and noun make the search intent reasonably obvious.

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?

The top-level description offers no explicit guidance about when to prefer this tool over get_exchange_rate or other search tools. Some usage direction is embedded in the criteria parameter description, such as filtering on SourceCurrencyCode and AsOfDate to read one rate, but this is implied usage rather than explicit selection guidance.

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