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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the bar is lower; the description usefully discloses what the result contains — a picture plus price and the colours the design can be printed on — which matters because there is no output schema. It does not, however, mention defaults for colour/garment beyond what the schema states.

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?

A single front-loaded sentence that packs purpose, parameter summary, and return payload without filler. It is dense but readable, and nothing egregious is wasted.

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?

As a read-only preview tool with no output schema, the description reasonably covers the essentials by naming the visual output and the accompanying price and colour availability. The main omission is any routing cue versus draw_shirt/check_drawing, which an agent needs in this crowded sibling set.

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 60%, so the schema documents most fields (colour default, garment options, design_id origin). The description restates the parameter set (garment='cut', colour, print size s/m/l, side) and parenthetically re-states the enum values rather than adding meaning like which combinations are valid or how colour accepts a name or id.

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 states clearly what the tool produces: a rendered picture of a design on a real shirt with its price and compatible print colours. The verb is implicit ('A picture of...') rather than action-first, and it never distinguishes itself from the similarly named sibling draw_shirt, so an agent has to infer that this is a preview rather than a drawing generator.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives, despite the presence of closely related siblings draw_shirt, check_drawing, and draw_from_photo. The description describes the output but not the workflow position or prerequisites (e.g. that design_id must come from a drawing).

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