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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note on behavior for missing/deleted templates, no pagination or expansion options, no scoping constraints.

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 short, front-loaded sentence with zero waste, but that is because it says almost nothing. Its brevity is under-specification rather than disciplined concision.

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?

This is a simple single-record lookup with a fully documented one-parameter schema and complete annotations, so little beyond a bare sentence is strictly required. Still, the description never states that the returned template can be passed to update_template or used with send_message, information an agent would plausibly need.

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?

There is only one required parameter (id) and schema description coverage is 100%, so the schema itself documents the input. The description neither clarifies the id format nor adds any meaningful semantics on top of it, which is the baseline expectation here.

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 restates the title and name nearly verbatim: "Retrieve a template" adds no specificity beyond the tool name get_template. It does not say what a template is, what fields come back, or how it differs from list_templates or get_template's update/delete siblings.

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 when-to-use guidance is given. With siblings like list_templates (enumeration) and create_template/update_template/delete_template alongside it, the agent gets no explicit statement that this is the single-record fetch keyed by id, though the id parameter implies it.

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