wa_list_templates

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

No annotations are provided, so the description carries the burden. It indicates this is a read-only operation by using the verb 'list', but does not disclose pagination behavior (the limit parameter) or whether the result includes all statuses beyond approved/pending. There is no mention of rate limits or output structure.

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?

One sentence with no wasted words, directly states the tool's function. It is appropriately sized for a simple list operation.

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?

The tool has only 2 simple parameters and no output schema, so the description is somewhat sufficient. However, it gives no information about what the response contains, how pagination works, or how limit affects results. For an agent selecting the tool, this is minimally viable but leaves some uncertainty.

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?

The schema has 0% description coverage, so the description must compensate. It clarifies that 'waba_id' refers to a WABA (WhatsApp Business Account), which adds some meaning. However, it does not mention the 'limit' parameter at all, leaving it undefined apart from the schema's type/default.

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 clear resource 'message templates' and scope 'approved/pending', and specifies the context 'for a WABA'. This clearly distinguishes it from sibling tools like wa_create_template, wa_delete_template, and wa_list_phone_numbers.

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 explicit guidance on when to use this vs alternatives. The purpose is implied: use when you need to see approved/pending WhatsApp message templates. However, it doesn't mention any exclusions or prerequisites, so the guidance is only implicit.

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