whatsapp_set_group_join_approval

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

Annotations already declare the mutation profile (readOnly=false, idempotent=true, destructive=false), and the description adds meaningful context beyond them: admin-rights prerequisite, the exact behavioral consequence of enabling, and that a success confirmation is returned.

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 sentences, front-loaded with the action, then the effect, then the prerequisite and return. Every sentence earns its place, including the return-value note given there is no output schema.

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 two-parameter toggle with no output schema, the description covers action, effect, prerequisite permission, related follow-up tool, and return shape — nothing an agent needs to invoke it correctly 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?

Schema coverage is 100% (baseline 3), and the description genuinely enriches the otherwise terse 'Enable or disable' by explaining what 'on' actually does to link-joiners, which is the semantics an agent needs to set the boolean correctly.

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+resource (turn group join approval on/off) and immediately explains the observable effect, which cleanly separates it from siblings like whatsapp_set_group_member_add_mode and whatsapp_set_group_locked.

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?

Gives clear context: it requires admin rights and points to whatsapp_get_group_requests for the resulting approval queue. It does not, however, explicitly say when to prefer this over the adjacent add-mode/locked settings tools, so the agent must infer the boundary.

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