get-template

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

The description implies a read-only operation ('reading the full contents'), which is transparent. However, it does not explicitly state that the tool has no side effects or is non-destructive, which could be clearer. No annotations are provided to contradict.

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 three sentences, front-loaded with purpose, returns, and exclusions. Every sentence adds value without redundancy.

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 simple tool (1 parameter, output schema exists), the description covers the essential aspects: when to use, what it returns, and when to use alternatives. It is complete for effective tool selection.

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 schema has 0% description coverage, leaving the parameter 'id' with no explanation. The description adds context ('by id' and mention of list-templates for obtaining it), but does not provide additional details like format or constraints beyond the schema.

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 it is for reading the full contents of a saved template by id, listing the returned fields (name, subject, recipients, body). It also distinguishes from sibling tools like list-templates and use-template.

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 includes explicit 'Use when' and 'Do not use when' conditions, specifying when to fetch the id from list-templates and when to use use-template instead. This provides clear guidance on tool selection.

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