list_whatsapp_templates

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool 'shows' templates, implying a read-only operation, but gives no details about pagination, permissions, or side effects. For a list tool, the lack of information about returned data structure or limits is a gap.

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 very short (one sentence) and front-loaded with the main action. However, the inclusion of '[query]' is unclear and seems like a placeholder. The description could be more informative without adding length, but it is not overly verbose.

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 simplicity (one optional filter, no output schema), the description is minimally adequate. It conveys the basic operation but does not specify return format or whether results are paginated. For a list tool, agents would benefit from knowing what fields are returned.

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% (one parameter 'category' described as 'Filtrar por categoria de plantilla'). The description adds no extra meaning beyond the schema. Baseline score of 3 is appropriate since the schema adequately documents the parameter.

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 clearly states 'Listar plantillas de WhatsApp' (list WhatsApp templates) and adds 'Muestra las plantillas de mensajes guardadas' (shows saved message templates). The verb 'listar' and resource 'plantillas de WhatsApp' are specific. However, the trailing '[query]' is ambiguous and slightly detracts from clarity. It distinguishes from sibling tools like get_whatsapp_template (single) and delete_whatsapp_template.

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 guidance on when to use this tool versus alternatives like get_whatsapp_template or list_whatsapp_workflows. No exclusions or context provided. The agent must infer usage from the name alone.

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