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

With no annotations provided, the description carries the full behavioral burden and discloses nothing: no permission requirements, no note on what happens if the number is already a participant or lacks a WhatsApp account, no rate-limit or privacy caveats, and no mention of side effects or return value.

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?

It is short, but this is under-specification rather than conciseness: a single noun-phrase fragment conveys no more than the tool name already does, so its brevity is not earned.

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 mutation tool with two required, fully undocumented parameters, no annotations, and no output schema, the description is missing nearly everything an agent needs: parameter formats, preconditions, side effects, error behavior, and the difference from sibling group-management tools.

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 description coverage is 0% for both parameters, so the description must compensate and does not. It never explains the expected format of group_id or phone_number (e.g., country-code inclusion, group JID format), leaving the agent to guess.

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 states a clear verb ('add') and resource ('group participant') plus platform context ('WhatsApp Web'), so the basic action is understandable. However, it is essentially a restatement of the tool name and offers no differentiation from siblings like remove_group_participant or list_group_participants beyond the obvious verb change.

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?

There is no guidance on when to use this tool versus alternatives such as create_group or remove_group_participant, nor any stated preconditions (e.g., the caller must already be an admin/member of the group). Nothing indicates 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.