whatsapp_get_group_participants

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

The description states 'Read-only', which simply restates readOnlyHint=true already present in annotations, and adds nothing about rate limits, permissions, pagination, or failure modes. With annotations covering safety, the description contributes no behavioral context beyond what structured data provides.

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, front-loaded sentences. The final sentence 'Returns the participants' largely duplicates the opening clause, so it is slightly redundant rather than wasteful.

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 simple one-parameter read tool with no output schema, the description is minimally adequate: it indicates the returned entities and their admin-status field. It omits any indication of result ordering or whether the caller is included, but nothing critical to invocation is missing.

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 a single parameter and schema description coverage is 100% ('Group JID'), so the schema already carries the semantic burden. The description adds no format or identifier guidance beyond it, making 3 the appropriate baseline.

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 ('List a group's participants') plus the payload detail ('with their admin status'), which cleanly separates it from write-side siblings like whatsapp_update_group_participants. It stops short of naming an alternative, but the purpose itself is unambiguous.

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?

No when-to-use, when-not-to-use, or alternative tooling is mentioned. The agent must infer that this is the read counterpart to update_group_participants purely from the name.

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