zernio_list_whatsapp_groups

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

No annotations are provided, so the description must cover behavioral traits. While 'List' implies a read-only operation, the description does not disclose potential side effects, required permissions, rate limits, or response characteristics (e.g., pagination). It is adequate but lacks depth.

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, clear sentence with no redundant words. It effectively communicates the tool's purpose in minimal space.

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 description lacks output schema and does not mention what fields the returned list includes, pagination, or sorting. For a list tool with one required parameter, it is minimally adequate but could be more complete to guide the agent on expected results.

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% (the only parameter 'accountId' has a description). The tool description does not add extra meaning beyond the schema. Baseline score of 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?

The description clearly states the action ('List'), resource ('WhatsApp Group chats'), and scope ('managed through a connected WhatsApp Business account'). It effectively distinguishes from sibling tools like 'zernio_get_whatsapp_group' (singular) and 'zernio_create_whatsapp_group'.

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 no guidance on when to use this tool vs alternatives. Given many sibling tools (e.g., 'zernio_get_whatsapp_group' for a single group, 'zernio_add_whatsapp_group_participants' for group management), it fails to clarify the appropriate context or exclusion criteria.

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