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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds genuine domain behavior the annotations cannot: the official API's 24-hour free-form messaging window and the fact that only approved templates deliver outside it. It stops short of describing return volume or pagination, which keeps it from a 5.

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 compact sentences, front-loaded with the core action, then the domain rule, then the downstream routing. Every sentence earns its place, though the middle sentence is more context than an agent strictly needs to execute the call.

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 two-parameter read tool with full schema coverage and rich annotations, the description covers purpose, the operational rule behind templates, and how the results feed other tools. Return-value shape and pagination are absent, but with no output schema that gap is minor.

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 the id and status parameters (including the APPROVED default) are already documented. The description reinforces that the session must be an official API session, which adds useful meaning to the id parameter, but adds nothing about the status filter. Baseline 3 is appropriate.

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 ('List'), resource ('message templates'), and a scope qualifier ('on an official WhatsApp Business API session, provider meta'). This is enough for an agent to distinguish it from sibling list tools like neuron_list_whatsapp_contacts or neuron_list_channels without opening any schema.

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?

Explicitly routes the agent to the consumers of this listing: neuron_send_whatsapp / neuron_compose_message / neuron_create_broadcast with messageType 'template', and explains the rule (24-hour window) that determines when a template is even needed. When and how-to-follow-up are both stated.

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