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

With no annotations provided, the description carries the burden of disclosure. It correctly implies a read-only operation via 'List' and notes that versions are immutable, but it does not mention pagination, ordering, response shape, or any other behavioral details an agent might need.

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 extremely concise with no filler or redundancy. It is front-loaded with the core action, though it is closer to a fragment than a fully structured description.

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 list operation with fully documented parameters, this is minimally viable, but it lacks context about what 'versions' means, what the output contains, and when to choose this over related template tools. Since there is no output schema, the description should provide at least some return-value context.

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?

The input schema already documents both required parameters at 100% coverage, so per the rubric this is a baseline 3. The description adds no extra detail about the parameters, but the schema sufficiently explains template_id and organization_id.

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 action ('List') and resource ('immutable versions'), and the tool name ties it to template versions. It is distinguishable from sibling tools like commsharbor_template_get and commsharbor_templates, though it could more explicitly say 'template versions' rather than relying on the name.

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 given for when to use this tool versus alternatives, and no exclusions or conditions are stated. The intended use is only implied by the tool name and parameters.

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