List WhatsApp Message Templates

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds the env var requirement and the return structure (name, status, category, language, components), which goes beyond the annotations. No contradiction.

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?

The description is compact and front-loaded with the main verb and resource. The env var prerequisite, args, and return are all covered in a few lines without wasted words. Every sentence earns its place.

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 simple list tool, this description is complete: it states the purpose, a critical prerequisite, the main parameters, and the return shape. The annotations cover safety, and the schema covers all parameter details. No output schema exists, but the description provides sufficient return info.

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 coverage is 100%, so the baseline is 3. The description repeats limit and status semantics but omits response_format. It adds no new information beyond what the schema already provides, so no bonus beyond baseline.

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 uses a specific verb 'List' with a specific resource 'message templates' and scopes it to the WhatsApp Business Account. This clearly distinguishes it from sibling send/update/mark tools. The purpose is immediately clear.

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?

The description provides clear context: it lists templates and requires the WHATSAPP_BUSINESS_ACCOUNT_ID env var. It doesn't explicitly name alternatives or exclusion criteria, but the distinction from send/update siblings is implicit and the env var prerequisite is a useful usage hint.

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