Compare Shopify Collections

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety. The description adds meaningful behavioral context beyond annotations, noting exact handles (not fuzzy matching) and listing the specific attributes compared. This gives a clear expectation of comparison semantics.

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 and largely efficient. It lists all key comparison areas in a compact presentation. It loses a point due to the awkward repeated 'collection collections' phrase and because 'Compare exact collection' initiation could be clearer.

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 low-complexity tool with 100% schema coverage and read-only/idempotent non-destructive annotations, the description is largely sufficient. It conveys the main purpose and comparison fields. It does not define output format, but in the context of a comparison tool, comfortable to infer output shape from the listed fields.

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% (stores and handles both have descriptions). The description adds no further detail about parameter padding, formats, or conventions beyond what the schema already provides. Baseline 3 is appropriate when the schema covers all parameters consistently.

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 operation (Compare) on a specific resource (exact collection handles) across stores and enumerates the compared fields. This distinguishes it from sibling compare tools (compare_catalog, compare_inventory, compare_prices). Minor typo 'collection collections' slightly reduces clarity but does not undermine intent.

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 usage for cross-store collection comparison but gives no explicit when-to-use, when-not-to-use, or alternatives guidance. An agent can infer from the resource name that this is for collections, not inventory or prices, but no explicit routing is provided.

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