Duplicate Shopify Product

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

Annotations already declare this is a non-destructive write operation, and the description adds useful behavioral detail: the copy defaults to DRAFT status so it cannot accidentally go live. It does not contradict any annotation and adds safety-relevant context beyond the 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?

Two short sentences, front-loaded with the action and scope, followed immediately by the default-status safety note. Every sentence earns its place with no filler.

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 four-parameter duplication tool with no output schema, the description covers the core operation, what is copied, and the default status. The only notable gap is the unmentioned includeImages parameter, but annotations already carry the mutation safety profile.

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 only 50%. The description maps newTitle ('under a new title') and newStatus ('defaults to DRAFT') and implies productId, but it never mentions includeImages, leaving one parameter with no explanatory text in either the schema or the description.

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?

States a specific verb and resource: copy a product including its variants and options under a new title. This clearly distinguishes it from generic create/update product tools in the sibling list.

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 to use it: duplicating an existing product with its variants and options, rather than creating a blank product. It does not explicitly name alternatives or exclusions, but the core condition is implicit and strong.

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