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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'Read one template,' which signals a non-mutating operation, but it does not mention permissions, return payload, error behavior, or whether a missing template produces a 404. This leaves notable gaps for a bare GET-like tool.

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 words long, with no filler, repetition, or unnecessary detail. It is concise and front-loaded with the core action and resource.

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 low-complexity tool with two required string parameters and no nested objects or enums, the description plus schema is minimally viable. However, with no output schema and no annotations, the agent has no stated expectation about what a successful read returns or how errors are surfaced.

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% for both required parameters, so the schema already provides the necessary meaning. The description adds no extra parameter guidance, which is acceptable given the schema is self-sufficient.

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 states a specific verb and resource: 'Read one template.' The word 'one' distinguishes it from the plural templates list and from sibling operations like template_create, template_update, template_archive, and template_preview. An agent can immediately tell what this tool does.

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 that this tool is for fetching a single template, but it does not explicitly explain when to choose it over alternatives such as template_versions, template_export, or templates. Usage context is present but mostly left to inference from sibling names.

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