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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds genuinely new behavioral facts: the metadata is cached, has a freshness signal, and participant rosters are deliberately unavailable at launch. That explicit limitation disclosure is exactly the kind of context annotations cannot carry.

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?

Two compact sentences with the resource and its returned metadata front-loaded, then the roster exclusion. The parenthetical is dense but every element (count, role, freshness) tells the agent something distinct.

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?

An output schema exists, so return values need not be spelled out, and the description still previews the key fields and a hard limitation. The only real gap is routing guidance against the many sibling get_* tools.

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 single conversation_id parameter is undocumented in both schema and description. The description only implies it identifies a group; it does not say the value is numeric (pattern ^\d+$) or where to obtain it, e.g., from list_groups.

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 names a specific verb-resource pair ("One WhatsApp group conversation") and enumerates what comes back (participant count, your role, cache freshness), so the agent knows this is a single-group detail fetch rather than a list. It does not explicitly distinguish itself from list_groups or get_group_activity, but the singular scope differentiates it implicitly.

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: the required conversation_id signals "call this when you already have a group ID," but the description never says when to prefer it over list_groups, get_conversation, or get_group_activity. No exclusions or prerequisites are stated.

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