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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds genuine value beyond that by disclosing the shape of the result set and by explicitly bounding its scope ('never the template markup'). It stops short of mentioning pagination or result ordering, which for a list endpoint would be useful.

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?

A single sentence, front-loaded with the resource, and every clause earns its place: the field list tells the agent what it will get and the closing clause rules out the one thing agents might wrongly assume (markup).

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 and no parameters, the description carries the return-value burden and does so adequately by enumerating the fields. For a zero-argument list tool only ordering/pagination behavior is left unspecified, which is a minor omission.

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 the schema-to-description burden is nil and the baseline of 4 applies. Nothing in the description misrepresents or adds confusion about inputs.

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 the resource specifically ('the organisation's Ironfang Render templates') and enumerates the fields returned (id, name, size, expected variable names), which is far more concrete than restating the name. It implicitly separates itself from render.template.get by asserting it never exposes template markup, though it doesn't name that sibling outright.

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 implied rather than stated: by promising 'never the template markup', an agent can infer that markup requires render.template.get or render.template.render, but no explicit when-to-use or when-not-to-use condition is given for choosing among the template siblings.

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