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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully adds that this is an expensive rendering operation producing the final output, which helps with cost planning, but it says nothing about what is returned (URL, binary, variant ID), whether the result is persisted, or any auth/quota requirements.

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?

Two short sentences with zero filler; the core action is front-loaded and the cost warning follows immediately. Nothing could be removed without losing information.

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 five-parameter rendering tool with no output schema, the description leaves a notable gap: it never says what the call returns or that the produced variant can subsequently be fetched via layerre_get_variant or listed via layerre_list_variants. The cost warning is helpful, but return-value behavior and failure modes remain unexplained.

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 every parameter including nested override properties is already documented in the schema. The description adds only the high-level framing of template plus optional layer overrides and no syntax, defaults, or constraints beyond what the schema provides, so the baseline of 3 applies.

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 and resource ('Generate a variant (rendered image) from a template') and clarifies the output is a rendered image with optional layer overrides. It distinguishes itself from layerre_create_template and layerre_create_layer by naming the product ('variant'), but it does not explicitly differentiate itself from the sibling layerre_create_variants_bulk, which an agent must infer from the singular 'a variant'.

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 'expensive operation' warning implies that callers should avoid this for bulk or repeated work (pointing implicitly at layerre_create_variants_bulk), but no alternative is named and no explicit when-to-use/when-not-to-use condition is given. Usage 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.