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 fully covered. The description adds that bodies contain `{{variable}}` placeholders, which is genuinely useful content-shape context, but says nothing about pagination behavior or how results are ordered.

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?

A single compact sentence with no filler, and the distinguishing detail (`{{variable}}` bodies) is placed early. It is efficient, though its terseness is part of why other dimensions suffer.

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?

With no output schema, the description should convey what a returned template looks like (id, name, body, locale, status) and how pagination works. Neither is present, so an agent knows what the tool fetches but not what it receives back.

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 0% — neither `page` nor `per_page` has a description, and the description text says nothing about pagination, defaults, or result limits. For a list tool the page/per_page semantics are exactly what the description should compensate for, and it does not.

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 resource (SMS templates) with a distinguishing qualifier that these hold `{{variable}}` bodies, so an agent won't confuse it with list_sms_campaigns or list_sms_messages. The verb 'list' is only implied by the name/prefix `[read]` rather than stated, and no explicit sibling routing is given.

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?

There is no statement of when to call this versus related tools such as render_sms_template, get_sms_campaign, or the generic list_templates. The agent must infer usage entirely from the tool name.

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