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

Beyond the annotations (readOnlyHint false), the description discloses key behavioral constraints: one free preview per store, no account required, and the need to poll with get_preview_status. It also clarifies that the generating is free and produces a 2K image, adding meaningful context for the agent.

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 extremely concise—two sentences—and front-loaded with the most critical constraint (one free preview per store). Every word adds value, with no filler or repetition of schema details.

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 has 4 parameters (2 required) and an output schema, the description covers the prerequisite (audit_store work order), the free/limit constraint, and the follow-up polling step. It is sufficiently complete for an agent to select and invoke the tool correctly without additional context.

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 100%, so the baseline is 3. The description adds limited extra meaning beyond the schema, mainly connecting store_url and garment_image_url to an audit_store work order, which the schema already partially states. No significant new parameter-level details are provided.

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 free 2K on-model try-on preview, specifying the exact inputs (store and listing photo URL) and distinguishing it from the paid create_tryon_job and the polling get_preview_status. The phrase 'taste before buying credits' reinforces its specific purpose.

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 conveys when to use the tool ('taste before buying credits') and provides usage context (one free per store, no account needed, from an audit_store work order). However, it does not explicitly name the paid alternative or state when not to use it, so it falls short of explicit when/when-not guidance.

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