waha_list_groups

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It implies a read-only operation ('List'), but doesn't mention authentication requirements, rate limits, pagination behavior (beyond what's in the schema), or what the output looks like (no output schema). This leaves significant gaps for a tool that interacts with WhatsApp groups.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse at a glance.

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 complexity of WhatsApp group management and the lack of annotations and output schema, the description is insufficiently complete. It doesn't address authentication, error handling, return format, or how it differs from related tools like 'waha_list_chats', leaving the agent with critical gaps in understanding how to use this tool 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 description coverage is 100%, with clear documentation for all three parameters (session, limit, offset). The description adds no additional parameter semantics beyond what's already in the schema, such as clarifying the scope of 'all' groups or how pagination works. This meets the baseline for high schema coverage.

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 'List all WhatsApp groups' clearly states the verb ('List') and resource ('WhatsApp groups'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'waha_get_group' (singular) or 'waha_list_chats' (broader scope), but the specificity is adequate for basic understanding.

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 versus alternatives. It doesn't mention sibling tools like 'waha_get_group' for retrieving a specific group or 'waha_list_chats' for a broader list including individual chats, nor does it specify any prerequisites or contextual constraints for usage.

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