shopify_create_product

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

No annotations provided, so the description carries full burden. It states 'Returns product + userErrors', indicating the return structure. It also notes the default status is ACTIVE, providing transparency on default behavior. However, it does not mention idempotency or side effects like publishing, but these are reasonable for a creation tool.

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?

Very concise: two short sentences. Each piece of information is essential – the action, required/optional parameters, status enum with default, and return value. 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?

Given no output schema, the description outlines return (product + userErrors) adequately. It covers all input parameters listed in the schema. For a simple creation tool, this is mostly complete, but it lacks guidance on relationships with other tools (e.g., after creation, use shopify_update_product to modify).

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 0%, so the description must compensate. It lists the required ('title') and optional fields with the status enum values and default. However, it does not explain the meaning of 'handle', 'productType', 'vendor', or 'tags', leaving ambiguity. Adds value over bare schema but insufficient for full understanding.

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 starts with 'Create a new product', a clear verb+resource pair. It lists required and optional fields, distinguishing it from siblings like shopify_archive_product or shopify_update_product.

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?

No explicit guidance on when to use this tool versus alternatives such as shopify_update_product or shopify_archive_product. The context is implied by the name 'create', but the description does not state 'use this for new products' or exclude other use cases.

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