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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the description doesn't need to restate safety. It does add real value beyond them: 'Refreshes' indicates the result is fetched fresh from WhatsApp rather than served from cache, and it enumerates the returned states plus the rejection reason, which matters since there is no output schema.

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 tight sentences, front-loaded with the action and followed by the return values; nothing superfluous. The repeated 'one ... or one' is slightly redundant but harmless.

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 three-parameter read with no output schema, the description covers the action and the outcome values, which is the most important missing structured information. It still leaves the did_id/draft_id/template_id selection rule and the required argument 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 0%, so the schema gives no parameter meaning, and the description only partially compensates. 'One template or one draft' hints that template_id and draft_id are mutually exclusive alternatives, but that is never stated outright, and did_id is never explained nor is which identifier is required.

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 and resource: it re-checks ('refreshes') the status of one WhatsApp template or one draft, and names the possible outcomes. It is distinguishable from list_whatsapp_templates (listing) and submit/revise/draft (which change templates), though it never names those siblings explicitly.

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 when-to-use guidance at all: nothing says to call this after draft_whatsapp_template or submit_whatsapp_template to poll for approval, and nothing says when to prefer list_whatsapp_templates instead. There is only an implied post-submission polling use case that the agent must infer.

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