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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes further by spelling out the exact side effects that are NOT performed (no draft, no order, no charge, no approval, no production) and by stating the layer-type limitation for agents. That is precisely the operational context an agent needs before invoking a validator with a price output.

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 tight sentences ordered by importance: action and returns first, layer constraint second, side-effect exclusions last. No filler, though the middle clause about artwork is partially redundant with the schema's own 'Agents cannot attach artwork' note.

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 complex nested-schema tool with no output schema, the description usefully covers the return shape (structured issues, preview link, price estimate) and the safety profile. The remaining gap is that it does not hint at the required design structure or what kinds of issues validation can surface, which would help an agent prepare a correct payload.

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?

Only one top-level parameter with a deeply nested schema at 0% reported description coverage, so the description carries a real burden. It does add the critical constraint that only text layers can be authored by an agent (artwork must come from the browser studio), but says nothing about the design envelope itself — version, templateId, matchSides, or quantity semantics are left entirely to the schema.

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?

States a specific verb ('Validate') and a specific resource ('festival scarf design') and enumerates the three return artifacts (issues, preview link, price estimate). The scarf-vs-jersey distinction is carried by the resource name, letting an agent separate it from prepare_jersey_design without opening either 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?

The stateless clause ('does not save a draft, create an order, charge money, approve artwork or start production') tells the agent this is a validate-only step in a pipeline, and 'artwork is uploaded in the browser studio' frames the workflow context. However, it never names an alternative tool or an explicit precondition for calling it, so the routing guidance is implied rather than stated.

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