Compare Shopify Prices

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds that it 'highlights mismatches or missing variants,' which is useful behavioral context. It does not contradict annotations, but it also doesn't disclose error handling or partial-match behavior. Given the strong annotation coverage, a 3 is appropriate.

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 zero filler. It clearly states the action, scope, and expected output in a compact structure. Every word earns its place, making it easy to scan.

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 read-only comparison tool with two well-documented parameters and comprehensive annotations, the description covers the core information: what is compared, across which stores, and what it returns (highlights of mismatches/missing variants). It lacks explicit mention of error handling or edge cases, but given the low complexity and the safety profile already provided, this is a minor gap.

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 coverage is 100% for both parameters, with the schema already describing stores as 'Configured store alias' and skus as 'One to fifty exact SKUs to compare.' The description doesn't add parameter-specific syntax or format details beyond the schema; it only reinforces the tool's purpose. Baseline 3 applies.

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') and clearly identifies the resource ('price and compare-at price for exact SKUs across selected stores'). It distinguishes itself from sibling tools like shopify_compare_inventory or shopify_compare_catalog by focusing on pricing rather than inventory or catalog content, so an agent can tell them apart without opening schemas.

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 its usage (when you need to compare prices across stores) but does not explicitly state when to prefer this over similar sibling tools (e.g., shopify_compare_inventory) or mention any exclusions or conditions. It leaves the agent to infer the right tool from the resource being compared.

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