qbo_deposits_update

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

Describes sparse-update (only provided fields changed) and SyncToken requirement (fetch first). No disclosure of error behavior, side effects, or authorization needs. Without annotations, more detail expected.

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, no fluff. Could be more precise about required fields but overall concise.

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?

Lacks explanation of return values (no output schema), no example usage, and does not reference sibling tools or clarify required field discrepancy. Incomplete for a tool with 8 parameters and nested objects.

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 has 100% description coverage. Description adds value by explaining SyncToken retrieval and sparse-update semantics. However, it incorrectly refers to 'Id' instead of depositId and says only two required fields vs schema's four.

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?

Description clearly states 'sparse-update an existing Deposit record', using a specific verb and resource. It distinguishes from sibling tools like create, get, and list.

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?

No explicit when-to-use or when-not-to-use guidance. The sparse update behavior is implied but no comparison with alternatives or prerequisites beyond SyncToken mention.

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