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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower, and the description still adds real value: it discloses the exact response shape, explains where descriptions come from, and warns that the file body is not returned. It does not mention pagination or catalog size limits, which are minor gaps for a read-only list.

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?

Purpose and source are front-loaded, followed by the return shape, field semantics, the boundary about missing file bodies, and the contribution path. Every sentence carries distinct, actionable information with no padding.

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?

There is no output schema, so the description carries the burden of describing the return value — and it does so field by field, including the meaning of `prompt` and the optional `referenceUrl`. Combined with the explicit no-argument statement, an agent has everything needed to call and interpret this 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 and the description confirms this with 'No arguments.', matching the empty object schema. With no parameters to disambiguate, there is nothing further to add, though it also does not hint at any future filtering options.

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 names a specific verb and resource: listing HTML templates and explorable archetypes from the public template catalog, and it gives the source repository URL. That is far more precise than a tautology. It does not, however, differentiate itself from the ambiguous 'catalog' sibling, which an agent could plausibly confuse with this one.

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 the operating context clearly (no arguments, public catalog, descriptions sourced from frontmatter) and draws a useful boundary: this tool does not return the file body, so the agent must open `url` for HTML and hatch notes. It stops short of explicitly routing among siblings (e.g. catalog/list/lookup), so the guidance is clear but not exclusionary.

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