Compare Shopify Collections

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral detail about what is compared: titles, sort order, product counts, SEO fields, and collection images. It does not describe handling of missing handles, but this is not a major gap given the annotation coverage.

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. Every phrase adds information: the operation, the resource scope, and the specific fields involved.

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?

The description is sufficient for a simple comparison tool, but there is no output schema and no statement about return format, missing handles, or how differences are presented. Given the tool compares up to 100 stores and 50 handles, a sentence about result structure or handling missing values would make it more complete.

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 100%, and both parameters ('stores' and 'handles') are already documented in the input schema. The description restates 'exact collection handles' and lists comparison fields, which adds output context rather than new parameter-level meaning. This aligns with the baseline 3 for high schema coverage.

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 uses a specific verb ('Compare') with a clear resource ('exact collection handles') and scope ('across stores'). It also lists the exact fields involved, making the tool's purpose unambiguous and distinguishable from comparison siblings like shopify_compare_inventory, shopify_compare_prices, and shopify_compare_catalog.

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 phrase 'across stores' implies the intended use case: comparing the same collection handles across multiple configured stores. However, the description does not explicitly state when to choose this tool over related tools such as shopify_compare_catalog or shopify_get_collection, nor does it mention exclusions or prerequisites.

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