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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds genuinely new context: what each result contains (one-line summary, preview image URL, colour variants), that multiple designs of one document share the same data shape, and that it works without an API key — a real auth disclosure. It stops short of saying whether the list is paginated or how large it is.

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?

Front-loaded with verb and resource, then the routing condition. The long parenthetical document-type list is the only bloat, but it earns its place by giving the agent vocabulary to match user requests.

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, the description usefully compensates by describing the per-item fields and the shared-data relationship across designs. Only the total result size / pagination behavior is unstated, which is a minor gap for a zero-argument list tool.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly frames this as a no-argument browse operation rather than implying filters exist.

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 ('List') plus resource ('Pressa's public document templates') with a concrete enumeration of the template types returned. The listing behavior is distinguishable from get_public_template and render_public_template by implication, though the description never names those siblings to make the routing explicit.

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 states a clear selection condition: use when the user wants one of these documents and has no layout of their own, or wants to browse designs. It does not name the alternatives (get_public_template for a single design, render_public_template to produce output), so the 'when-not' half is left to inference.

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