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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description's extra burden is lower. It still adds value beyond them: the response includes linked groups, and it warns that community and group names are third-party content to treat as data rather than instructions — a real behavioral caution an agent would otherwise miss.

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?

Three short sentences, front-loaded with the scope and read-only nature, followed by the safety note and the next-step routing. No sentence is redundant or padded.

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?

With one required parameter, an output schema that covers return values, and full annotation coverage, the description supplies everything else an agent needs: scope, safety handling of untrusted names, and where to go for group messages.

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?

There is only one parameter and schema coverage is 100%, with the schema already saying 'Community id from list_communities' plus a pattern and length bounds. The description adds no format or sourcing detail beyond that, so the baseline of 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?

The first sentence gives a specific verb and resource ('Read one WhatsApp community's details and its linked groups'), and the singular 'one' plus the linked-groups scope distinguishes it from the sibling list_communities, which enumerates communities.

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?

It explicitly routes the agent elsewhere for a related need ('To read messages of a linked group, find its conversation via list_groups / list_conversations'), and the schema note ties the id to list_communities. It stops short of stating when not to call this tool, but the alternative path is clear.

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