whatsapp_get_group_requests

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

Annotations already cover readOnlyHint=true and openWorldHint=true, so the description's 'Read-only' is redundant, but it adds real value beyond the annotations: the admin-rights authorization requirement and the return shape (requesting user JIDs). It does not mention pagination, result limits, or behavior on a non-approval group, keeping it short of a 5.

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?

Four short sentences with zero filler, front-loaded with the core action and followed by the precondition, safety profile, and return value. Nothing is wasted and nothing important is buried.

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?

There is no output schema, and the description compensates by naming the returned data (requesting user JIDs), along with the auth requirement and read-only nature. Missing only edge-case behavior (empty results, pagination, non-approval groups) to be fully complete.

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 100% ('Group JID' is documented in the schema), so the baseline is 3. The description only restates 'a group' and adds no format, JID syntax, or scoping detail beyond what the schema already provides.

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 (List), a specific resource (pending requests to join a group), and the precondition that scopes it (groups with join approval enabled). The verb contrast with the sibling whatsapp_update_group_requests is clear enough that an agent can pick correctly without opening either schema.

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 gives a prerequisite ('Requires admin rights') which is genuinely useful, but never states when to choose this over the sibling whatsapp_update_group_requests (approve/reject) or what happens when the group has join approval off. Usage is implied by the verb rather than spelled out.

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