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

No annotations are provided, so the description carries the full burden. It prominently discloses the draft-only behavior, the approval-gated publishing process, and the sensitive-tier approval requirement. It lacks detail on error conditions or side effects (e.g., whether it overwrites existing products), but the key behavioral constraints are well covered.

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 composed of two clear paragraphs. The first is front-loaded with the key behavior (create draft, never live) and the fields set. The second paragraph includes routing and approval details — useful, but slightly redundant with the first paragraph's 'publishing is a separate approval-gated step' and the explicit routing line. Slight redundancy prevents a 5.

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?

This is a mutation tool with no output schema, but the description clearly states what it does (creates a draft product), what it doesn't do (publish), when to use it, and the approval implications. Given the 100% parameter schema coverage and clear behavioral transparency, the description is complete for an agent to decide and use the tool safely.

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?

The input schema already provides 100% coverage of all six parameters with clear descriptions (e.g., 'Product title', 'Vendor/brand name'). The description adds the context that title, description, vendor, type, and tags are the fields set, but does not add semantics beyond the schema for parameters like companyId or description_html. Baseline 3 is appropriate since the schema handles the heavy lifting.

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 tool creates a new product in Shopify as a DRAFT, explicitly noting it's never live and that publishing is a separate approval-gated step. It lists the fields it sets (title, description, vendor, type, tags), which distinguishes it from sibling tools like create_shopify_discount_code, create_shopify_page, update_shopify_product_draft, and publish_shopify_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?

The description explicitly states when to use the tool ('Use when building out the catalog') and what happens next ('the operator approves go-live later'). It also includes routing guidance ('Shopify: create a DRAFT product... never live') and notes the approval tier, providing clear context that differentiates it from publishing tools.

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