whatsapp_set_group_member_add_mode

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

With no annotations, the description carries the full burden of disclosure. It fails to mention that this tool likely requires admin privileges, what side effects occur (e.g., change in group permissions), or how the system responds to invalid inputs.

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?

The description is extremely concise (one sentence, 5 words) and front-loaded. However, it may be too brief, lacking context that would fit in a short paragraph without becoming verbose.

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?

Without annotations or an output schema, the description is incomplete. It does not explain the tool's effect on group state, error conditions, or confirmation feedback. For a mutation tool, this is a significant gap.

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 100% and already describes the boolean parameter. The description adds minimal value beyond restating the schema's purpose. It does not provide examples or clarify edge cases (e.g., default behavior).

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 clearly states the verb 'control' and the specific resource 'whether only admins can add members.' It distinguishes this tool from sibling tools like whatsapp_set_group_announce or whatsapp_set_group_locked by focusing on the member add permission.

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 description provides no guidance on when to use this tool versus alternatives (e.g., other group settings). It does not mention prerequisites (like admin rights) or situations where this should not be used.

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