Update Inventory Item

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

Annotations only indicate the operation is not read-only and not destructive, leaving the description to carry the burden. The description adds meaningful behavior: PATCH semantics, cost per call, and the API-key requirement. It omits edge-case behaviors like not-found responses, but the main mutation risk is clearly disclosed.

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?

A single, front-loaded sentence plus a parenthetical cost/auth note. Every word delivers value, and the key PATCH semantics are stated first. For what it attempts, it is optimally 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?

For a 19-parameter mutation tool with low schema coverage, the description is insufficient. It lacks when-to-use guidance, required-parameter emphasis, alias handling, idempotency behavior, and error cases. The output-schema presence covers return values, but the input-side and usage context remain incomplete.

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 low at 42%, so the description needed to compensate for the many undocumented parameters. It does not: no parameter is mentioned, no aliases such as subtype/item_type or request_id/idempotency_key are explained, and the required inventory_id is not called out. The schema itself provides whatever little parameter meaning exists.

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 conveys PATCH semantics, which implies partial update of an inventory item, and the tool name supplies the resource. It clearly differentiates from add_inventory_item or archive_inventory_item by its update nature, though it does not explicitly name the resource or contrast siblings.

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?

The phrase 'unspecified fields untouched' provides an important usage contract: this tool is for partial updates rather than a full overwrite. However, there is no explicit guidance about when to choose it over add_inventory_item or other update tools, and no prerequisites such as requiring an existing item.

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