shopify_create_collection

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

Annotations already cover the write/destructive profile (readOnlyHint=false, destructiveHint=true), so the bar is lower. The description adds useful context beyond annotations: the manual-vs-smart distinction and the channel-publishing side effect. However, it does not explain the destructive risk flagged by destructiveHint=true for a create operation, nor the confirm authorization gate.

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?

Two short sentences (~20 words) with zero wasted language. The core purpose is front-loaded and the second sentence adds a targeted parameter behavior. Every word earns 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?

This is a complex tool (9 params, nested ruleSet/image objects, no output schema, non-idempotent, destructive annotation) yet the description is minimal. It omits how manual vs smart collection parameters relate, default publication behavior when publicationIds is absent, and any indication of return values or the confirm requirement. An agent has too little context to call this correctly on the first try.

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 only 11% schema description coverage (only 'confirm' is documented), the description carries the burden of explaining 9 parameters but only addresses publicationIds. The manual-vs-smart phrasing vaguely implies productIds vs ruleSet but never states which parameter drives which behavior, leaving most parameters semantically 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?

The description states a specific verb+resource ('Create a manual or smart collection') that clearly distinguishes it from update/get/search siblings. However, the second sentence about publishing overlaps conceptually with shopify_publish_resource's domain, and no sibling is named to disambiguate.

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 implies when to use the tool (when creating collections) and gives a use-case hint ('Pass publicationIds to publish to explicitly selected channels'). But it offers no explicit exclusions or alternatives, leaving an agent to infer when update_collection, add_to_collection, or publish_resource would be more appropriate.

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