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

Annotations already cover readOnlyHint and openWorldHint, and the description adds useful context: the default status filter and what each returned template contains (components and required variables). Minor omission is any mention of pagination/result-size limits for larger template sets.

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?

Three short sentences, front-loaded with the core action and scope, with the usage rationale last. Little waste, though the 'approved ones by default' clause duplicates schema info.

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?

There is no output schema, and the description compensates by explaining that each template includes its components and variables needed to send it. Combined with the fully documented schema, an agent has enough to call it correctly; only pagination behavior is left unstated.

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 device, size, and status are already documented with defaults and constraints. The description only restates the APPROVED default, adding little beyond the schema – baseline 3 applies.

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?

States a specific verb ('Retrieve') and resource ('WhatsApp templates') scoped to a device, and clarifies that only approved templates come back by default. It doesn't name the sibling create/delete template tools to differentiate explicitly, but the list-vs-mutate distinction is obvious from the name and description.

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?

'This is required for sending template-based messages' gives a concrete use context, and '(approved ones by default)' implies when to override the status filter. However, no explicit when-not guidance or mention of the alternative tools for template management is given.

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