Find Duplicate Shopify SKUs

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description does not need to repeat that. It adds useful behavioral context by mentioning that incomplete scans are labeled when a store exceeds the row limit, which is information not available from the annotations or schema.

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 two sentences with no filler. The primary action is front-loaded, and the important caveat about incomplete scans is placed second where it is still easy to notice.

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 two-parameter report tool, the description covers the core behavior and an important boundary condition caused by the row limit. It does not describe the exact return format, but the schema and annotations handle parameter and safety details sufficiently for correct invocation.

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 the 'stores' and 'first' parameters are already documented in the input schema. The description adds only the row-limit concept that aligns with 'first' but does not meaningfully extend parameter understanding beyond the schema.

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 and resource: it finds duplicate SKUs within each store and SKUs shared across stores. This clearly separates it from sibling report and query tools like shopify_low_stock_report or shopify_catalog_health.

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 gives clear context for when the tool is appropriate: when duplicate or cross-store SKU overlaps need to be detected. It does not explicitly name alternatives or exclusion conditions, but the purpose statement itself provides enough guidance for an agent to select it.

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