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

The description adds a key behavioral fact beyond the annotations: that the tool creates an accounting entry rather than moving money. This is crucial because the name alone might suggest a bank transfer. The annotations already indicate a non-read-only, non-destructive write operation, so the description's contribution is valuable but not comprehensive (e.g., no mention of permissions or side effects).

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 short and front-loaded with the main action. The three sentences each add essential information: what it does, what kind of entry it is, and what it does NOT do. There are no wasted words, though it could be slightly more compact by merging the first two sentences.

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 description, combined with the schema, provides enough information for an agent to invoke the tool correctly. It covers the crucial non-obvious behavior (not moving money) and the schema covers parameter constraints. It omits any mention of permissions or the response format, but for a simple create operation with full schema coverage, this is acceptable.

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?

The input schema has 100% description coverage, with detailed documentation of the entity object (required FromAccountRef, ToAccountRef, Amount; accounts must differ) and the company parameter. The tool description adds no additional parameter-level information, so it relies fully on the schema. 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 clearly states the action ('Create') and resource ('transfer in QuickBooks Online'), and adds a clarifying definition ('An accounting entry recording a transfer between accounts'). It explicitly distinguishes itself from actual bank transfers, which is a common source of confusion and helps differentiate it from other tools. This is a specific, unambiguous purpose statement.

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 includes an explicit exclusion: 'It does not move money between bank accounts.' This tells the agent when NOT to use this tool and implies the tool is for accounting entries only. However, it doesn't name a specific alternative tool for actual bank transfers, so the guidance is clear but incomplete.

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