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

With no annotations, the description carries the behavioral burden. It discloses that templates are frozen, that the return includes the full content, and that the revision digest pins the exact revision an attempt was prepared against. It does not cover errors, authorization, or rate limits, but for a read operation the disclosed semantics are substantive.

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?

Two sentences with zero filler. The core action and scope are front-loaded, and the second sentence adds only the most relevant behavioral nuance, the revision pinning, without waste.

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 single-parameter read tool with no output schema, the description is complete: it names the resource, enumerates the return contents, and explains the revision semantics an agent would need to select appropriate templates. Nothing essential is missing.

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%, so the baseline is 3: the schema already documents task_id as 'Task template identifier'. The description adds context about what a task template is and why the revision digest matters, but it does not add parameter-level format or usage details beyond the schema.

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 (Read) and resource (one frozen task template) and then enumerates exactly what is returned: question, inputs, assumptions, comparison basis, limitations, and revision digest. This clearly distinguishes it from siblings like list_task_templates (plural listing) and get_resource (generic resource).

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 makes clear this is the tool for reading one full task template, especially when revision-pinned details are needed. It does not explicitly name alternatives or state when not to use it, but the single-template-versus-list contrast with list_task_templates gives adequate contextual guidance.

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