get_template

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

With no annotations, the description carries the transparency burden. It discloses that this is a read operation via 'Retrieve' and 'GET', and mentions optional merge behavior. It does not address error responses or confirm whether merging is transient, but for a simple GET the core behavior is clear.

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, front-loaded sentence with the endpoint appended. Every word adds value; there is no filler.

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 read operation with one required parameter and two schema-documented optional parameters, the description plus schema is enough to call it correctly. There is no output schema, but 'Retrieve an email template' sufficiently indicates the expected result.

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 67%, and the two richer parameters (extraQuery and mergePersonId) are documented in the schema. The description adds minimal extra meaning for id ('by id') and mergePersonId ('optionally merging fields'), which is adequate but not detailed.

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 ('Retrieve') and resource ('email template'), and specifies the lookup mode ('by id'), which separates it from list_templates. The GET endpoint reinforces exactly what operation is performed.

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 when to use the tool (fetching a single template by id, optionally with merge fields), but it does not state when to prefer list_templates or post_templates_merge instead. No exclusions or alternative routing are provided.

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