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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description adds real behavioral context: results are ordered by newest activity, participant counts are cached (potentially stale), and group subjects are member-controlled UNTRUSTED content requiring prompt-injection caution. The security warning is a material disclosure not available from any structured field.

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 short sentences, zero filler, with the resource and ordering front-loaded and the security caveat attached directly to the field it concerns. Every clause carries information the agent needs.

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?

The output schema covers return values, so omitting them is fine, and the untrusted-content warning is a strong addition. However, for a paginated list tool with 0% schema description coverage, the absence of any limit/cursor semantics leaves a noticeable hole.

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% and the two parameters (limit, cursor) get no explanation in the description. 'Newest activity first' hints at ordering but says nothing about the 50-result cap or how cursor-based pagination works, so the description fails to compensate for the schema gap.

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 the specific resource (WhatsApp group conversations) and its default ordering, which separates it from get_group (single group) and list_communities. It never states an explicit verb like 'list' and doesn't explicitly route to sibling tools, so it falls 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?

There is no when-to-use guidance: nothing says to prefer get_group for details on a specific group, or list_conversations for chats generally. Ordering is stated but there are no exclusions or alternatives, so the agent must infer the appropriate call context.

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