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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: signed URLs in the result are auto-refreshed when expired, which tells the agent the response may carry refreshed credentials. It omits ordering and the default page size, which are minor.

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 waste: the primary action and scope come first, and the signed-URL refresh note follows as secondary context. Nothing is repeated from the title or schema.

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 simple three-parameter read tool with full annotation coverage, full schema coverage and no output schema, the description covers purpose, scope and one non-obvious behavioral trait. Only result ordering and pagination guidance are left implicit, which is a small gap.

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%, with skip, limit and template_id all documented inline including the default of 100 and the 1000 cap. The description adds only the framing that the listing is scoped to one template; it provides no pagination or UUID-format detail beyond the schema, so the baseline 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?

"List all variants for a specific template" gives a specific verb (list), resource (variants) and a scope constraint (per template), which separates it from layerre_get_variant (single fetch) and layerre_list_templates (different resource). It never names a sibling explicitly, so it sits just short of a 5.

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: the required template_id tells an agent this is the path when enumerating variants of one template. There is no explicit when-not guidance and no mention of when to prefer layerre_get_variant for a single record or how this relates to create_variants_bulk.

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