Find Duplicate Shopify SKUs

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds a meaningful caveat beyond that: scans can be incomplete when a store exceeds the row limit, and the report labels those cases, which is important for correctly interpreting results.

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 sentences with no filler. The main purpose is front-loaded, and the caveat is stated immediately after, making the description highly scannable.

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 report with fully documented parameters and rich annotations, the description conveys what the report outputs—duplicate SKUs and shared SKUs—and its main caveat about incomplete scans. It does not enumerate output fields, but no output schema exists and the stated scope is sufficient for selecting and invoking this tool.

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%, so the schema fully documents both stores and first. The description does not need to repeat parameter details; the row-limit caveat is related to first, but the schema already explains the maximum scan count.

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 opens with concrete verbs and a specific resource: finding duplicate SKUs both within each store and shared across stores. This scope clearly separates it from sibling report tools like shopify_low_stock_report or 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 description clearly states when an agent would want this report—when duplicate SKUs need to be detected inside or across stores—so the use case is evident. It does not name alternatives or explicit exclusions, but the purpose is specific enough to avoid confusion with most sibling tools.

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