create_product

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

Annotations only declare openWorldHint=true, so the description carries real weight and delivers: embroidery routing to real placements with derived Printful thread colors, fill-by-default for face goods, and that generate_mockup auto-derives variants so mockup_variant_ids is unnecessary. It does not cover failure modes, auth/permission needs, or what the call returns, so it falls short of a 5.

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 purpose and the standalone constraint are front-loaded, and the pipeline routing is condensed into one sentence. It is dense but not wasteful; the main deduction is the trailing stray artifact "[#e8704a]" and a very long single paragraph that is harder to scan than bulleted clauses.

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-param, nested-object creation tool with no output schema and minimal annotations, the description supplies the missing context: what state the product lands in, how garment-specific defaults resolve, and the downstream calls needed to publish it. An agent has enough to invoke it correctly.

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 only 40% schema description coverage, the description compensates well: it explains print_style defaults per garment class, thread_colors' embroidery-only scope and auto-derivation, and generate_mockup's variant derivation. It says less about garment, pricing, workspace, and design_url, leaving some of the 10 params thin.

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?

Starts with a specific verb+resource ("Create a STANDALONE product from a design") and immediately scopes it ("it is NOT placed on any store yet"), which cleanly separates it from ship_product and the sync_* siblings. An agent can classify this tool 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?

Explicitly names the required follow-on sequence (add_variants -> sync_to_fulfillment -> sync_to_channel) and the alternative ("To run that whole pipeline in one call instead, use ship_product"). This is exactly the when-to-use/when-to-use-something-else guidance the dimension asks for.

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