list_join_requests

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds the administrator permission requirement, which annotations do not convey. It still says nothing about pagination or result volume for a growing request queue.

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 front-loaded sentence with the resource first and the access constraint second; nothing is wasted. It is short to the point of being under-specified, but structurally sound.

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 explained, and the read-only/profile context is covered by annotations. The gap is that neither description nor schema defines what identifier 'chat' should contain, which is the one thing an agent must get right to call this tool.

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 0%, so the description must compensate and it largely does not. 'D'un groupe' loosely maps to the required 'chat' parameter but gives no expected format (JID, phone number, group name), and the optional 'account' parameter is entirely unexplained.

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 resource and scope: pending join requests for a group awaiting approval. The qualifier 'en attente d'approbation' implicitly separates it from the sibling handle_join_requests (which acts on those requests), though the sibling is never named.

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 states a prerequisite ('il faut en être administrateur'), which is real usage guidance, but gives no explicit when-to-use/when-not-to-use framing and never points to handle_join_requests as the follow-up action. Usage is implied rather than directed.

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