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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, fully covering the safety profile. The description adds nothing beyond that — no note on pagination behavior, ordering of results, or what a "site template" represents. It does not contradict the annotations.

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 short sentence that is trivially front-loaded, but it is under-specified rather than genuinely concise — the sentence earns its place only as a restatement of the title, carrying no extra information.

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?

This is a simple, zero-required-parameter read tool with rich annotations and no output schema. The description covers the bare minimum, but with no output schema an agent gets no hint about what the returned template objects look like or how pagination results are ordered.

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%: limit and offset are both documented in the schema with defaults, ranges, and meanings. The description contributes no additional parameter meaning, but the schema baseline of 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 your site templates" restates the tool name and title almost verbatim, adding no distinguishing detail. It does contain a verb and resource, but an agent gets no information about scope, filtering, or how this differs from get_site_template or list_sites.

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?

There is no indication of when to use this tool versus the sibling get_site_template (single item) or the create/update/delete template tools. No prerequisites, exclusion conditions, or alternatives are mentioned, so the agent must infer everything from the name.

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