create_store_product

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

The description adds behavioral details beyond annotations: it notes authentication via API key, a max of 10 concurrent requests, and respect for read-only and dry-run modes. It also clarifies that creating a product is not destructive (consistent with annotations), and implies it is a write operation without idempotency.

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 well-structured with a clear first line for the primary purpose, followed by necessary details. It could be slightly more concise, but every sentence adds value and the structure is logical.

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 the tool's complexity (6 parameters, output schema exists), the description covers the most important aspects: what the tool does, when to use it, parameter semantics, and behavioral constraints. The presence of an output schema means return values need not be detailed, and the description mentions returning a JSON object.

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?

With 0% schema description coverage, the description provides detailed explanations for all 6 parameters, including the purpose of each and an example for 'variants'. It adds significant meaning beyond the raw schema, such as the optional nature of 'additional_fields' and the use of 'account' with a reference to 'list_accounts'.

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 clearly states the action 'Create a product in a store' and specifies the resource and the requirement for at least one variant. It distinguishes this tool from siblings like 'create_store_product_variant' and 'create_store_product_image' by focusing on the core product creation.

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 explains when to use this tool (custom/headless storefronts) versus relying on automatic syncing from Shopify or WooCommerce. It also provides context about variants being required and mentions authentication and concurrency limits, guiding appropriate usage.

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