zernio_list_whatsapp_contacts

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

The description does not disclose behavioral traits beyond what is implied by the schema (pagination via limit/offset). It mentions 'connected WhatsApp Business account' as a prerequisite but does not elaborate on rate limits, data freshness, or whether 'all' contacts are truly returned given pagination defaults. With no annotations, the description carries the full burden but only partially addresses it.

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 with no extraneous words. It is front-loaded with the key action and resource, making it easily scannable.

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 list tool with simple parameters and no output schema, the description is nearly complete. However, it could mention that pagination is supported via limit/offset (already in schema) and clarify that 'all' may be limited by the max limit. Overall, it provides enough context for correct usage.

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%, and the description adds no additional parameter meaning beyond what the schema already provides. The schema describes 'accountId', 'limit', and 'offset' adequately, so the description does not need to elaborate further. Baseline 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') and the resource ('all WhatsApp contacts') with a specific scope ('for a connected WhatsApp Business account'). It distinguishes from sibling tools like zernio_get_whatsapp_contact (single contact) and zernio_list_whatsapp_contact_groups (groups).

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as zernio_get_whatsapp_contact for a single contact or zernio_bulk_create_contacts for creation. No prerequisites or limitations are mentioned.

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