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

The annotation readOnlyHint=true already discloses the safe read-only nature, so the description doesn't need to repeat that. It adds some context (that templates are 'ready-to-use' and lists categories) but does not elaborate on return format, pagination, or any potential limitations beyond what the annotation covers.

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?

One concise sentence that is front-loaded with the action and resource, followed by useful examples. Every word earns its place with no redundancy.

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?

For a simple list tool with a readOnly annotation, a single well-documented parameter, and no output schema, the description is adequate. It clearly states what the tool returns (a list of 26 templates) and provides examples. Could mention the language parameter, but the schema already covers that.

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 single parameter 'lang' is fully described in the schema (Language: es, en, fr) with 100% coverage. The description adds no additional parameter semantics, but since the schema carries the meaning, the baseline of 3 is appropriate.

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 uses a specific verb ('List') and clearly identifies the resource ('business templates') with a specific scope ('26 ready-to-use'). It also gives examples (CRM, Hotel, etc.), making it easy to distinguish from sibling tools like template_install.

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?

The description clearly implies when to use this tool (to see available templates) and the context is straightforward. However, it does not explicitly mention alternatives or when not to use it, though the sibling name 'template_install' provides a natural contrast.

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