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 only the approval-mode precondition; it says nothing about return shape, ordering, or pagination, so it adds modest value beyond the structured data.

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 sentence with zero filler; the resource and the scoping condition are front-loaded so the agent can decide immediately.

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 three-required-parameter read tool with no output schema, the description covers purpose and applicability but leaves the return payload (what a join request record contains, pagination) unspecified, which is the one thing the absent output schema would otherwise carry.

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, group_id is not), and the description adds no parameter-level meaning beyond implying a WhatsApp group. With middling coverage the description should compensate for the undocumented group_id format but does not.

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 precise resource ('pending join requests on a WhatsApp group'), and a scoping precondition ('join_approval_mode approval_required'). This clearly separates it from the sibling approve/reject and group participant tools without needing to open a 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?

The 'approval_required' condition tells the agent the context in which this tool is applicable (only groups using join-approval mode will have pending requests). However, it never names alternatives (e.g. whatsapp_group_join_requests_approve/reject) or states exclusions, so it stops short of explicit when/when-not guidance.

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