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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description does not need to establish that this is a write. It adds one useful fact, that the response carries the SyncToken. However, it omits validation failure modes and the fact that the schema itself flags forbidden PII fields.

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 sentences, zero padding, and the operation is front-loaded ahead of the return-value note. Every sentence earns its place.

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, the description's SyncToken note partially covers return values, and the heavy nested-object requirements live in the schema. But for a mutation against a real accounting ledger, the absence of any guidance on company selection or when a deposit is the correct record type leaves a gap.

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 parameters and the nested Deposit requirements (DepositToAccountRef, DepositLineDetail.AccountRef, forbidden PII fields) are already fully documented. The description adds nothing beyond the baseline, so a 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?

States a specific verb and resource (create a deposit in QuickBooks Online) and even names the return shape. It is distinguishable from siblings by the 'deposit' resource, though it never explicitly contrasts with near-neighbors like create_payment or create_transfer.

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?

There is no when-to-use guidance, no prerequisites (e.g., a connected company or a bank account), and no routing to alternatives such as create_transfer for moving funds. The agent must infer everything about invocation context.

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