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

Annotations already cover safety (readOnly, non-destructive, closed-world), so the description's real value is disclosing that results come from the local store and can be stale. That staleness/freshness caveat is exactly the kind of context annotations cannot convey; it stops short of describing pagination or ordering.

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?

A single sentence with a parenthetical caveat: the core action leads, the sync precondition and the JID hand-off follow. Nothing is redundant.

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 zero-required-parameter read tool with an output schema and full annotation coverage, it supplies the missing pieces: data source staleness, recovery step, and how the return value is consumed downstream.

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 all three parameters (limit, query, account) are documented in-schema. The description adds no parameter guidance of its own, so baseline 3 applies.

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?

States a specific verb and resource: lists WhatsApp groups the account is a member of, and adds the value of the returned JID. It scopes to 'groups' rather than all chats, which implicitly separates it from whatsapp_list_chats, but it does not explicitly name a sibling or contrast with whatsapp_group_info.

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?

Gives a concrete prerequisite ('run whatsapp_sync first if a just-created/joined group is missing') and a downstream continuation (use JID as chat_id for read/send). It does not, however, say when to prefer this over whatsapp_list_chats or whatsapp_group_info.

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