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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds meaningful behavior beyond that: it changes on-hand quantities and books a valuation difference (side effects), constrains to US Plus/Advanced companies, and notes the returned record carries a SyncToken. This is solid added context.

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?

Three short sentences, front-loaded with the action, then the effect/constraint, then the return. No filler; each sentence carries distinct information.

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 object schema and no output schema, the description covers purpose, side effects, eligibility, and the return value (saved record + SyncToken). Nothing essential to correct invocation is missing.

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%, with the nested 'entity' object fully documented (TxnDate, DocNumber, AdjustAccountRef, ItemAdjustmentLineDetail, QtyDiff/NewQty). The description adds no parameter syntax beyond the schema, so the baseline of 3 applies.

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+resource ('Create an inventory adjustment in QuickBooks Online') and further states the effect ('Changes the quantity on hand of inventory items and books the valuation difference'). This clearly distinguishes it from update_inventory_adjustment, delete_inventory_adjustment, and get_inventory_adjustment.

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 a concrete eligibility precondition: 'US companies on Plus or Advanced only.' That is useful when-to-use context, but it does not explicitly route the agent to alternatives or state when-not-to-use (e.g. use update vs create).

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