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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds important behavioral context beyond that: the optimistic concurrency requirement (current SyncToken) and the fact that it returns the saved record with a new SyncToken. It does not detail what fields are destroyed or the sparse-update default, but those are covered in the schema.

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, front-loaded with the core action and prerequisites, and the return value follows immediately. Every clause carries needed information without repetition or filler.

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 mutation tool with a nested entity parameter, no output schema, and rich schema descriptions, the definition covers the essential call prerequisites, return behavior, and safety annotation. It omits some schema-documented details like sparse update behavior and deletion limitations, but those are clearly present in the entity schema.

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 the schema already documents the entity and company parameters in detail. The description reinforces the need for Id and SyncToken but adds no new syntax or format beyond what the schema provides, making the baseline 3 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 gives a specific verb and resource: 'Update an existing item in QuickBooks Online.' It distinguishes update from create implicitly by saying 'existing,' but does not name sibling tools like create_item or get_item for contrast.

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?

It states the required concurrency inputs (Id and current SyncToken as returned by the last search or write), which tells the agent what it must have before calling. It does not explicitly compare with alternatives such as create_item or search_items, so no exclusions are given.

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