Create Shopify Collection

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

Annotations already declare the write/non-idempotent/non-destructive profile, so the description adds real value by disclosing the irreversible constraint that a rule set cannot be added after creation. It does not discuss rate limits, failure modes, or return payload, but the immutability warning is the critical behavioral fact for this tool.

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?

Front-loads the core action and the manual/smart fork, uses a concrete ruleSet example, and avoids padding. The bulleted structure is scannable, though the trailing note about rule-set immutability is slightly buried at the end where it arguably belongs up front.

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 6-parameter, nested-object, no-output-schema tool, the description covers the hardest concept (ruleSet) and the key constraint well, but several parameters with no schema documentation are left silent. An agent can call the smart path confidently but gets little help for seo, handle, or sortOrder.

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 17%, so the description must carry more weight; it does explain ruleSet, appliedDisjunctively, and common column values (going beyond the schema). However, it leaves seo, handle, sortOrder (an 9-value enum), and descriptionHtml entirely unexplained, so the compensation is partial.

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+resource ('Create a collection') and immediately splits it into two meaningful modes (Manual vs Smart), which is the key distinction an agent needs. It clearly differentiates itself from siblings like shopify_update_collection and shopify_collection_add_products by naming the latter as the follow-up for manual membership.

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 explicit guidance on which mode to pick and routes the agent to shopify_collection_add_products for manual product assignment. It also warns 'decide smart vs manual now', which is actionable, though it does not spell out when NOT to create a collection or prerequisites (permissions, naming collisions).

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