getTemplate

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only states the action ('Get an email template by ID') without describing what happens if the ID is not found, the return format, or any permissions/rate limits. This adds minimal value beyond what the name and input schema already convey.

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, front-loaded sentence with no unnecessary words. It efficiently communicates the essential purpose without redundancy, making it highly scannable for an AI agent.

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?

This is a simple getter with one parameter, no nested objects, and no output schema. The description is adequate for such a straightforward read operation, but it could be more complete by noting the response shape or likely error conditions. Given the absence of annotations and output schema, it sits at the minimal viable level.

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: the 'id' parameter is described as 'Template ID'. The description adds no further semantic detail beyond the parameter's existing description. Therefore, a baseline score of 3 is appropriate, as the schema fully documents the only parameter.

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 'Get' with a clear resource 'email template' and scope 'by ID'. This clearly distinguishes the tool from siblings like listTemplates (list all), createTemplate, updateTemplate, and mergeTemplate, while also separating it from getTextMessageTemplate by specifying 'email'.

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?

Usage is implied by the standard getter convention: retrieve a single template when you know its ID. No explicit when-to-use vs alternatives, exclusions, or prerequisites are provided. The description would be stronger if it mentioned that listTemplates is used for batch retrieval or search.

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