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

No annotations are provided, so the description carries the burden. It discloses PNG rendering and the WhatsApp send side effect. However, it omits the 'upload' action entirely, does not mention authentication requirements, and does not describe the response format or consequences of sending.

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 sentences, front-loaded with the tool's purpose, and no fluff. The template list and action guidance are packed into compact, useful phrasing.

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?

Given the tool's complexity (9 params, nested data object, no output schema, no annotations) the description covers core behavior and send side effects but leaves notable gaps: the 'upload' action, response/return details, and several parameter semantics. It is adequate for basic use but not fully self-sufficient.

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%, and the description compensates partially by listing template values and example data fields ('clientName, providerName, date, time'). Yet it leaves several parameters unexplained: apiKey, orgSlug, width, clientId, whatsappTo, and whatsappBody.

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 opens with a specific verb and resource: 'Render a communication template as a visual image (PNG)'. It lists the three available templates and distinguishes itself from sibling comms_send_message by emphasizing image rendering and WhatsApp attachment behavior.

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?

Provides actionable usage instructions: 'Use action "preview" to get the image URL, "send" to render and send via WhatsApp with the image attached.' This gives clear context on how to use the two main actions, though it does not mention the 'upload' action or explicitly contrast with comms_send_message for non-image sends.

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