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

Annotations already mark this tool as read-only and non-destructive. The description adds useful behavioral context: transfer records are accounting entries and this tool does not move money between bank accounts, preventing a common misinterpretation. It doesn't cover auth, rate limits, or side effects, but those are less critical for a read-only search.

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 short sentences with the main verb and resource front-loaded. The second sentence earns its place by clarifying the domain meaning of 'transfer', and there is no redundant restatement of the schema or annotations.

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 full definition provides company selection, flexible criteria, filtering constraints, pagination behavior, and read-only annotations. The only gap is the absence of an explicit output schema or return-field description, but for a search-over-records tool the description and schema are otherwise sufficient.

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%, and the schema's criteria description is rich—operators, ANDed filters, case sensitivity, pagination, and unsupported fields. The tool description itself contributes no parameter-level meaning, so it sits at the baseline 3.

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 first sentence names the action and resource explicitly ('Search transfer records in QuickBooks Online'), and the second sentence clarifies what a transfer is in this domain. It is clear, but it doesn't contrast with get_transfer or the other search_* siblings, so differentiation relies mostly on the tool name.

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 description implies the search use case but never says when to choose search_transfers over get_transfer or create_transfer. The schema's criteria text explains filtering behavior, but selection guidance among sibling tools is absent.

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