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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it says nothing about pagination via cursor, whether results default to the account's templates, or how search/date filters interact. With annotations doing the heavy lifting, this is a 2 rather than a 1, but there is no added behavioral context.

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 words are front-loaded but this is under-specification rather than conciseness. The length is not the problem; the absence of any useful content is.

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?

An output schema exists, so return values need not be explained, but for a seven-parameter listing tool the description omits pagination, filtering, and any usage context. It is not adequate to call the tool correctly without opening the schema.

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?

All seven parameters (limit, cursor, search, and four created/content-updated date bounds) have 0% schema description coverage, and the description mentions none of them. The agent cannot know from the definition that cursor pagination or date-range filtering even exists.

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 saved templates" essentially restates the tool name templates_list. It conveys a verb and a resource, but adds no scope, no notion of what a 'saved' template is, and no differentiation from templates_get, templates_update, or templates_reverse_engineer.

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 guidance on when to call this versus templates_get or templates_reverse_engineer, and no mention of prerequisites or typical scenarios. The agent is left to 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.