zernio_list_whatsapp_flows

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

The description does not disclose any behavioral traits beyond the basic action. It does not mention that the tool is read-only, whether it returns all flows or only those for a specific account, or any pagination or rate limiting behavior. With no annotations provided, the description carries the full burden but offers very little.

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 a single sentence without unnecessary words. It is front-loaded with the action and resource, but could benefit from a bit more detail on what the list contains.

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 parameter, no output schema), the description is incomplete. It does not explain what a WhatsApp flow is, what the response looks like, or whether the list is filtered by account. Sibling tools with similar purposes likely have comparable descriptions, but this one lacks sufficient context for an agent to use it effectively.

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 already describes the only parameter (accountId) as 'Filter by WhatsApp account ID'. The description adds no additional meaning about the parameter or its usage. Since schema coverage is 100%, the baseline is 3, and the description does not improve upon it.

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 the action ('List all WhatsApp flows') and the resource ('WhatsApp flows'). It implicitly distinguishes from sibling tools like 'zernio_get_whatsapp_flow' (singular) and 'zernio_create_whatsapp_flow', but does not explicitly differentiate from other list tools such as 'zernio_list_whatsapp_templates'.

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 is provided on when to use this tool versus alternatives, such as 'zernio_get_whatsapp_flow' for a single flow. There is no mention of prerequisites, context, or when not to use it.

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