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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds meaningful domain context beyond annotations by clarifying that a transfer is an accounting entry and 'does not move money between bank accounts,' which helps agents avoid conceptual misuse even though it is a read operation.

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 two short sentences with no filler. The core operation and identification method are front-loaded, and the additional accounting clarification is brief and relevant.

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 simple read tool with two parameters, one required, and annotations covering safety, the description provides enough context to select and invoke it correctly. It could mention return value shape or explicitly reference search_transfers, but those are minor gaps given the tool's simplicity.

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%, so both id and company are already documented in the schema. The description does not add parameter-level detail, but with full schema coverage the baseline 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 precise verb and resource: 'Get a single transfer from QuickBooks Online by Id.' It distinguishes itself by targeting a single transfer rather than a list, and the added domain context 'accounting entry recording a transfer between accounts' clarifies exactly what entity is being fetched.

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 usage when a specific transfer Id is already known, but it does not explicitly contrast with search_transfers or mention when to use an alternative. The 'by Id' phrasing offers some guidance, but there is no clear when-to-use versus when-not-to-use statement.

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