zernio_add_whatsapp_group_participants

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

The description only states the action ('Add participants'), which implies mutation, but lacks disclosure of behavioral traits like authorization needs, rate limits, idempotency, or side effects (e.g., what happens if participants are already in the group). Without annotations, the description carries the full burden and fails to provide sufficient transparency.

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 a single, focused sentence with no extraneous information. It is concise and to the point. While it could be enhanced with additional context, it avoids redundancy.

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?

Given the tool is a mutation with 3 required parameters and no annotations, the description is insufficient. It does not clarify return behavior, error conditions, or the state of the group after addition. For example, it does not mention that participants must be valid phone numbers or that the operation may fail if the group is full or the account lacks permissions.

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% with all parameters described inline. The description does not add any value beyond the schema; for instance, it does not clarify the expected format for phone numbers beyond what the schema already states ('with country code'). Baseline 3 is appropriate.

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 ('Add participants') and the resource ('existing WhatsApp Group'), making the tool's purpose immediately obvious. It distinguishes from the sibling tool 'zernio_remove_whatsapp_group_participants' implicitly by name and via the verb 'Add'.

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?

No guidance is provided on when to use this tool versus alternatives, such as the remove counterpart or other group-related tools. There is no mention of prerequisites (e.g., require group admin permissions) or when not to use it.

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