Update Shopify Collection

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only implicit partial-update scope by enumerating fields; it does not state whether omitted fields are left unchanged, whether SEO can be cleared, or what authorization is needed.

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 tight sentence with the verb and affected fields front-loaded and zero padding. It is efficient, though the brevity contributes to the missing usage and parameter detail noted elsewhere.

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 mutation tool with a required ID, a nested SEO object, and 20% schema coverage but no output schema, the description is too thin. It never explains partial-update behavior, the required collectionId, or the nested seo structure.

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 20%, so the description must compensate, but it names just title, description HTML, and SEO while omitting the plain 'description' parameter and the required collectionId entirely. The nested 'seo' object's inner title/description semantics are left undocumented.

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 (collection) plus the fields affected (title, description HTML, SEO metadata). An agent can distinguish it from shopify_create_collection and the add/remove-products siblings, but the description does not explicitly name or exclude those alternatives.

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 when-to-use context, no prerequisites (e.g. existing collection ID), and no pointer to competing collection tools such as shopify_collection_add_products. Usage must be inferred entirely from the name.

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