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

Annotations already state readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only nature is established. The description adds useful detail about what fields are returned and that groups are scoped to the account, but it does not disclose pagination, account identifier expectations, or potential empty results.

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 one sentences short and front-loaded. It gives the core action and result in a compact, readable em dash phrase with no redundant wording.

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 simple read-only list operation, the description is largely complete: it identifies the resource, the scope, and the returned fields. The annotations already cover side-effect/destructive aspects. It is slightly shy of full completeness due to missing any notes on account handling or result limits.

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 description coverage is 0%, so the description carries the burden of explaining the 'account' parameter. It does indicate that the account is the one whose groups are the listed entity, but it does not explain the expected format, optionality, or behavior when omitted.

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 precisely states the operation ('List WhatsApp groups'), the scope ('the account belongs to'), and the returned fields ('subject, jid, participants count, owner'). This makes it clearly distinct from sibling tools like whatsapp_group_members or whatsapp_chats.

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 about when to choose this tool over related alternatives such as whatsapp_chats or whatsapp_group_members. There is no mention of when not to use it, prerequisites, or alternative tools.

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