listTemplates

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List email templates' and fails to mention pagination, output format, permissions, or any side effects. This is a minimal behavioral description that does not enrich the agent's understanding beyond the name.

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?

The description is a single, concise sentence with no waste or redundant information. Every word earns its place, making it highly efficient and well-structured.

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 fully documented parameters, the description is adequate but sparse. It does not mention pagination behavior despite the pagination parameters, and with no output schema, it fails to indicate what fields are returned. This leaves some ambiguity about the exact response structure, but the core purpose is clear.

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 input schema has 100% coverage with descriptions for all three parameters (next, limit, offset). The description adds no additional parameter semantics, so the baseline score of 3 is appropriate as the schema already fully documents the parameters.

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 'List email templates' clearly states the action (list) and the resource (email templates), which differentiates it from sibling tools like listTextMessageTemplates and getTemplate. It is specific and unambiguous.

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 implies usage for listing email templates but does not explicitly mention when to use it versus alternatives. The word 'email' provides implicit differentiation from listTextMessageTemplates, but no alternative tools or exclusions are stated.

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