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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is well covered. The description adds only the id-or-alias lookup mode; it does not add not-found behavior, alias publication requirements, or other operational context beyond what annotations and schema provide.

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 a single front-loaded sentence with no redundant wording. It immediately states the resource and lookup mechanism.

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 read-only nature, rich annotations, full parameter schema coverage, and an output schema, the description is minimally adequate. However, it leaves ambiguity around what happens when both id and alias are provided or when neither is provided, which matters because no parameters are marked required.

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 100%, so the schema already documents both parameters, including that alias is an alternative to id. The description's 'by id or alias' mirrors that schema content rather than adding precedence rules, mutual-exclusivity details, or format semantics.

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 and resource ('Get a template') and adds lookup keys ('by id or alias'), which signals a single-resource fetch rather than a list operation. It does not explicitly distinguish itself from siblings such as list_templates or create_template, so it is clear but not fully differentiated.

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 implies usage when the caller knows a template id or alias, but it does not explicitly say when to use this versus list_templates or create_template. There is no guidance on when-not to use it, nor on behavior if neither id nor alias is supplied.

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