Update Inventory Item Settings

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

Annotations cover idempotency, non-destructiveness, and open-world behavior, so the bar is lower. The description nonetheless adds real behavioral detail: 'Only provided fields change' (partial-update semantics), HS codes have dots/spaces stripped, and countryHarmonizedSystemCodes 'replaces the whole override list' — a field-level data-loss behavior that the destructiveHint=false annotation does not convey. It is the reason an agent must re-read before calling.

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?

The front-loaded opening and bulleted grouping are readable, and the closing lines (read-back tool, SKU-or-id, partial update) are the highest-value content. However, most bullet entries restate the schema descriptions nearly verbatim ('requiresShipping: false for digital or service items', 'Province/state code e.g. BC'), so a meaningful share of the text does not earn its place.

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 9-parameter, zero-required, no-output-schema tool, the description covers every parameter with meaning plus normalization and list-replacement semantics, and names a sibling for verification. It is nearly complete; what is missing is the relationship to adjacent inventory tools (bulk update, inventory levels), which matters for choosing this tool correctly.

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?

With 100% schema coverage the baseline is 3; the description earns above that by adding normalization rules the schema lacks ('6110.20.20' and '61102020' both accepted), the purpose of each field (cost for COGS, requiresShipping false for digital), and the replace-not-merge behavior of the override array.

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 (update) and resource (a variant's inventory-item settings) and explicitly scopes it as the per-SKU attributes that are not pricing. The field list makes the boundary concrete. It does not, however, distinguish itself from the quantity-oriented siblings (shopify_adjust_inventory, shopify_set_inventory, shopify_bulk_update_variants), which an agent could plausibly pick for a value like 'tracked'.

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?

Points at shopify_get_variant_locations for reading current values and notes the tool accepts either a SKU or an explicit inventoryItemId, which is useful routing. But there is no when-to-use/when-not guidance relative to shopify_bulk_update_variants, shopify_update_product, or the inventory-level tools, and no preconditions are stated.

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