join_group_with_link

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

Describes behavioral details beyond annotations: joining creates a system message, new chat appears, and reversibility through leave_group (which is permanent). No contradiction with annotations.

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 concise sentences, each adding value: action, consequences and reversibility, related tool. No wasted words.

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?

Fully covers the tool's purpose, input, process, side effects, and return value for a simple join operation. Annotations and schema are well complemented.

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%, so baseline is 3. The description reinforces the parameter format (invite URL or bare code), adding slight extra clarity but not substantial new information.

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 action (join) and resource (WhatsApp group) with specific input format (invite URL or code). It distinguishes from siblings like get_group_invite_link and leave_group.

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?

Provides explicit when to use (join via invite), consequences (system message, chat appears), and alternatives (get_group_invite_link to create links, leave_group to reverse).

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