listTemplates

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

No annotations exist, so the description must convey behavior. It correctly implies a read-only list operation but fails to clarify pagination behavior (e.g., using limit/offset/next cursor) or any side effects. Important traits like rate limits or data freshness are omitted.

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 without fluff. It is appropriately front-loaded and wastes no words. However, additional details could improve informativeness without significantly increasing length.

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 absence of an output schema and the presence of three parameters, the description is too minimal. It does not explain return format, pagination behavior, or how 'next' cursor relates to limit/offset. For a list tool in a crowded sibling set, more context is needed.

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 coverage is 100% with descriptions for all three parameters (limit, offset, next). The description adds no extra context beyond the schema, so it meets the baseline of 3. The existing schema descriptions are adequate but generic.

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' uses a clear verb and resource, distinguishing it from listTextMessageTemplates (text message templates) among siblings. However, it lacks specifics on scope (e.g., all templates or filtered) and does not differentiate from other list tools beyond the resource name.

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?

No guidance is provided on when to use this tool versus alternatives like getTemplate (single) or listTextMessageTemplates (similar). There is no mention of prerequisites, conditions, or exclusions, leaving the agent to infer usage from the name alone.

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