get_template

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

Since no annotations are provided, the description carries full responsibility for behavioral disclosure. The word 'Fetch' indicates a read-only operation, and the phrase 'subject + content preview' clarifies that it returns a preview rather than full content. However, it could explicitly state that no modifications occur or mention any authentication requirements.

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 one concise sentence that is front-loaded with the core action and resource. It contains no unnecessary words, making it highly efficient and easy to parse.

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 tool with one parameter and no output schema, the description adequately communicates the return value (template with versions and content preview). It does not explain error conditions or provide broader context, but the description is reasonably complete given the tool's simplicity.

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 description coverage is 0%, but the single parameter 'template_id' is self-explanatory and the description repeats 'Fetch one template', implying the ID specifies which template to fetch. The description does not add explicit parameter detail, but the parameter name and context are sufficient for a simple identifier.

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 'Fetch' with a specific resource 'one template with its versions', clearly indicating a single-item retrieval operation. It also specifies the return content ('subject + content preview'), distinguishing it from siblings like list_templates which would list multiple templates.

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 is provided on when to use this tool versus alternatives such as list_templates or preview_email. The description only states what it does, leaving the agent without clear usage context or criteria for selection.

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