shopify_update_collection

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds 'with a before/after result', which reveals something about the return shape. However, it does not disclose that changes are permanent or that confirm=true is required, leaving behavioral transparency mostly to annotations and schema.

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 description is a single front-loaded sentence with no filler. It communicates the core purpose quickly, though the phrase 'fields, rules or image' is compact but somewhat imprecise. Overall it is appropriately 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 destructive mutation tool with 8 parameters, nested objects, no output schema, and a required confirm field, the description is incomplete. It lacks guidance on when confirmation is needed, how partial updates behave, what the before/after result actually contains, and what constraints apply to ruleSet or image. The description does not provide enough context for an agent to invoke this tool safely and 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 description coverage is only 13%, so the description must compensate for under-documented parameters. It only groups parameters into 'fields, rules or image' and fails to explain the semantics of id, store, confirm, ruleSet, sortOrder, descriptionHtml, or image. This is insufficient for an 8-parameter tool with nested objects.

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 states a clear verb ('Update') and resource ('collection'), and names the kinds of changes ('fields, rules or image'), distinguishing it from create_collection and get_collection. However, 'fields' is vague because the schema supports specific fields like title, descriptionHtml, and sortOrder, so it is not fully precise.

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 description gives no guidance on when to use this tool versus alternatives such as shopify_create_collection or shopify_update_product. It does not mention prerequisites, the confirm authorization step, or when to prefer another mutation tool. Usage is only implied by the tool name and the generic 'Update' verb.

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