getTemplate

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

No annotations provided, so description must cover behavioral traits. The description only states the basic function; it does not mention error behavior (e.g., if ID not found), permissions required, or rate limits. For a simple read, the risk is low, but the absence of detail is notable.

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?

One sentence without filler. Efficient but could add minor context without becoming verbose. The structure is front-loaded with purpose.

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 get by ID, the description covers the core purpose. However, without output schema, the agent has no information on the return type or structure. It is minimally adequate.

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 100% with a single parameter 'id' that has a brief description. The description adds no extra semantic meaning beyond the schema. Baseline 3 applies.

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 'Get an email template by ID' clearly states the action (get) and the resource (email template) with a specific identifier (ID). It distinguishes from sibling tools like listTemplates which retrieves multiple templates, and create/update/deleteTemplate which modify.

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 guidance on when to use getTemplate versus listTemplates or other get tools. There is no mention of alternatives or prerequisites. Agents must infer usage from tool name alone.

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