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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds return-shape context ('template summaries with optional layer details') and the folder/tag filtering notion, but says nothing about pagination behavior or result ordering 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?

Three short sentences with the core purpose front-loaded and no filler. The middle sentence overlaps slightly with the schema's include_layers description, costing a bit of economy but nothing is genuinely 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?

For a zero-required-parameter read tool with full annotation coverage and full schema coverage, the description covers identity, scope, return shape, and filtering. With no output schema present it could say a bit more about the summary fields returned, but nothing critical to calling it correctly is missing.

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 skip, limit, include_layers, and tag are already fully documented with defaults and bounds. The description only reinforces the tag parameter and adds the mild nuance that tags map to folders; it adds no syntax or format detail beyond the schema, so 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?

The description gives a specific verb and resource ('List all templates') and scopes it to the authenticated user, which cleanly separates it from layerre_get_template (single fetch), layerre_list_variants (different resource), and layerre_list_template_tags (tags only). It stops short of naming any sibling explicitly, so it is clear but not maximally differentiated.

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?

It offers one concrete usage cue: 'Use the tag parameter to filter by folder/tag.' Otherwise the when-to-use context is only implied by the verb – nothing says when to prefer this over get_template for a known ID, nor when to call list_template_tags first to discover valid tags.

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