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

With no annotations, the description carries the full burden and does disclose the two behaviors most likely to cause data damage: counts are absolute new values rather than deltas, and changing 'unit' relabels without converting quantities. It omits permission requirements, behavior on an unknown id, and what the call returns, keeping it short of a 5.

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?

Four short sentences, no repetition, and the highest-risk caveats (absolute counts, unit does not convert) are placed prominently. Every sentence conveys a distinct constraint that is not recoverable from the schema.

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 an unannotated mutation tool with a nested parameter object and no output schema, the description supplies the essential semantics an agent needs to avoid corrupting inventory data. Return values and failure behavior remain unspecified, which is a minor gap given no output schema exists to cover them.

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 0% across a nested object with eight fields, so the description must compensate. It meaningfully clarifies the null-means-unchanged convention, decimal UoM on counts, and the non-converting semantics of 'unit', but says nothing about msrp, notes, or the distinction between toShipCount, damagedCount, onOrderCount, and inventoryCount.

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 ('Edit') and resource ('an existing inventory item'), which lets an agent separate it from create_new_inventory_item and delete_inventory_item. It does not address the overlap with the sibling edit_inventory_item_name, even though this tool's schema also accepts a 'name' field.

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?

Gives real operating guidance for partial updates: 'If field is not to be changed then leave null' and 'Id field is required', which tells the agent how to invoke it minimally. There is no guidance on when to prefer this tool over edit_inventory_item_name, add_inventory_unit, or move_inventory_unit_quantity, so alternative selection is left to inference.

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