List All Templates

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

With no annotations, the description carries the behavioral burden but only states the basic retrieval action. It fails to disclose that the tool is read-only, that results are paginated (max 200), or that the 'all' scope is limited to the authenticated account. No behavioral warnings or limitations are conveyed.

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, focused sentence that efficiently conveys the core function. However, it could be slightly more informative without losing brevity, e.g., noting it returns a paginated list.

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 lack of output schema, the description should indicate what information is returned for each template (e.g., id, name, generation). It also fails to mention that the tool lists only the user's own templates, which is important for context. With many sibling tools, it does not help the agent decide between similar list tools.

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 description coverage is 100%, so the schema fully documents the two parameters. The tool description adds no additional meaning or context about how parameters interact or default behaviors (e.g., page_size default 50), meeting the baseline expectation.

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 tool retrieves all transactional templates, explicitly mentioning both legacy and dynamic categories. This differentiates it from sibling tools like get_template (single template) and list_single_sends.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., get_template for a specific template), nor does it mention any prerequisites or best practices for filtering or pagination.

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