Create Shopify Product

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent, open-world write. The description adds real behavioral context beyond them: the tool defaults to DRAFT (so nothing publishes by accident), a default variant is silently created when productOptions is omitted, and images require publicly reachable URLs. It does not disclose what the response contains, which matters since the downstream create_variants step needs the product's identity.

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?

Front-loaded with the core action and default status, then organized under clear "Options and variants" and "Images" headings. Tight and skimmable, with only a slight restatement of the imageUrls constraint already present in the schema.

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 10-parameter create tool with nested objects and no output schema, the workflow guidance is solid, but the description never says what comes back. Since it explicitly instructs the agent to call shopify_create_variants afterward, the missing note about the returned product ID (the handle needed for that next call) leaves a real gap for the documented workflow.

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 only 20%, so the description carries extra weight, and it does explain status's publish semantics, the productOptions shape, and the imageUrls public-URL constraint. However six of ten parameters (handle, vendor, productType, tags, seo, descriptionHtml) get no explanation beyond their self-evident names, so it only partially compensates for the coverage gap.

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+resource ("Create a product") and immediately scopes the variant/no-variant cases, which is what separates it from shopify_create_variants and shopify_update_product. An agent can tell exactly what this tool produces without opening the schema.

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?

Names the follow-on tools explicitly (shopify_create_variants for real variants, shopify_update_product to price a default variant) and gives the condition that selects each path. It stops short of a true when-not (e.g. "to copy an existing product use shopify_duplicate_product"), so it lands at 4 rather than 5.

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