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

No annotations are provided, so the description carries the burden. It discloses the scope ('user's templates') and the structure of each template, which is useful. However, it does not mention pagination, sorting, or explicitly state it is a read-only operation (though 'List' implies that). For a simple zero-parameter list tool, this is adequate but not exhaustive.

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?

Two sentences with no filler. The action is front-loaded, and the description efficiently conveys purpose, item structure, and a usage hint. Every word earns its place.

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?

Given the low complexity (no parameters, no output schema, no annotations), the description covers the essential facts: what the tool does, what it returns (templates with name, body, subject), and a typical use case. Minor gaps like pagination behavior are not critical for a simple list operation, so it is nearly complete.

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 has zero parameters, so the baseline score is 4. The description does not need to explain parameters and does not add parameter-related info, which is appropriate. It mentions template attributes but those relate to the return value, not 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 clearly states the verb 'List' and the resource 'the user's EMAIL templates', distinguishing it from other template tools like email_templates_create, email_templates_get, and sms_templates_list. It also adds useful context about template contents (name, body, subject).

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 gives a specific use case: 'Use this to find an existing template before drafting a new one.' It implies this is the go-to for listing existing templates, but does not explicitly mention alternatives or when not to use it. It clearly establishes the primary purpose.

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