shopify_update_prices

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

Annotations flag destructiveHint=true and idempotentHint=false, and the description substantially adds to that: exact-match SKU resolution vs Shopify's prefix search, duplicate/conflict rejection before any write, ambiguous-SKU skipping, read-back verification, per-item outcome and store status vocabularies, and result trimming that never drops non-applied items. This is unusually rich disclosure.

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?

One dense paragraph that front-loads the verb, resource, and scope before the resolution/validation/verification mechanics. Nearly every sentence carries operational value, though the outcome-status enumeration is somewhat heavyweight.

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?

No output schema exists, yet the description explains return values (per-item outcome, store status, trimming guarantees), edge cases (shared SKUs, conflicting duplicates), and safety (dryRun default). An agent has everything needed to call and interpret it 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?

Schema coverage is 80%, already documenting store, stores, dryRun, and allowDuplicates. The description reinforces the store/stores duality, the dryRun-default behavior, and the duplicate-SKU semantics, adding meaning beyond raw field names though not new syntax.

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 (set) and resources (price, compareAtPrice, unitCost) for a precise scope (up to 250 SKUs, one store or several in parallel), distinguishing it from sibling update_product. An agent can identify the operation and its granularity without opening the schema.

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 clear context for when to use it: bulk SKU-level price updates, store vs stores for parallel multi-store writes, and dryRun defaulted on. It does not name a specific alternative (e.g., shopify_update_product) for single-product edits, so it stops short of explicit when-not guidance.

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