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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the returned-field list (useful given no output schema) but says nothing about auth requirements for profile_id/phone_number_id or whether the participant list is truncated.

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 front-loaded sentence with no filler. The dense field enumeration is justified because there is no output schema, though the bare list reads as a data dump rather than prose.

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 read-only tool with annotations covering safety and no output schema, the field list meaningfully tells the agent what it receives. Remaining gaps (group_id format, auth context, participant list limits) are minor.

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 67%: profile_id and phone_number_id are documented in the schema, but group_id has no description anywhere. The phrase 'Read a WhatsApp group' only weakly implies group_id is the group identifier, adding no real detail beyond the schema.

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 ('Read') and resource ('a WhatsApp group') and enumerates the fields returned (subject, participants, created_at, is_suspended), which clearly separates it from whatsapp_groups_list and whatsapp_group_update. It never names a sibling explicitly, so it stops short of a 5.

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?

Usage is only implied: fetch one group's details given group_id. There is no statement of when to prefer this over whatsapp_groups_list, nor any prerequisite or exclusion, leaving routing to the agent's inference from the name.

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