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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description adds real value beyond them by enumerating what is returned (panel size, safe edge, patterns, fonts, layer types, artwork rules, USD prices by quantity) and flagging that checkout is not enabled yet — a constraint an agent would otherwise trip over.

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?

Three front-loaded sentences with no filler: what it lists, what it returns, and the checkout caveat. Dense but every clause carries information; the product-dimension detail is arguably the only slightly verbose element.

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?

With no output schema and no parameters, the description carries the return-value burden and does so by enumerating the returned fields. The only gap is workflow context — that this feeds prepare_scarf_design — and pricing tiers are mentioned but not characterized (currency, quantity breaks).

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 tool takes zero parameters, so the baseline is 4; there is nothing to mis-specify and the description correctly implies a no-argument listing call.

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?

Specific verb + resource + scope: it says it lists THE FRW custom festival scarf template and describes the physical product (two 25 x 72.25 inch panels, front/back can differ). This clearly distinguishes it from list_jersey_templates and from catalog search tools.

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?

Usage is only implied – an agent can infer it should call this before prepare_scarf_design to obtain specs, but the description never names that sibling or states when-not to use it (e.g., versus lookup_catalog or search_catalog). No prerequisites are stated.

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