get-template

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

No annotations provided. Description implies read-only behavior by stating 'reading full contents' and listing return values, but does not explicitly mention safety, permissions, or side effects. However, the description is clear enough for a simple retrieval tool.

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?

Three sentences: first states usage, second states returns, third states when not to use with alternatives. Front-loaded and concise with no redundant information.

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 tool's simplicity (one parameter, output schema present), the description covers all necessary aspects: what the tool does, when to use it, what it returns, and how it differs from related tools. The output schema handles remaining details.

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?

Only one parameter (id) with no description in schema. The description adds meaning by stating 'by id' and clarifying that 'id' refers to the template's identifier. The usage guidelines further advise using list-templates to obtain the ID if unavailable.

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 reads the full contents of one saved template by its ID, listing specific fields (name, subject, default to/cc, body). It distinguishes from siblings like list-templates and use-template by providing when-not-to-use guidance.

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?

Explicitly states when to use (reading full contents of a template by ID) and when not to use (no ID or want to apply template). Provides clear alternatives: list-templates to get IDs and use-template to apply the template into a draft.

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