whatsapp_reset_group_invite_link

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

With no annotations, the description must disclose side effects. It does not state whether this invalidates the old link, generates a new one immediately, or requires specific permissions. The agent is left guessing about the mutation's impact.

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 sentence, which is concise but overly brief for a tool with no annotations. It lacks structure (e.g., no context, no separate sections) and misses opportunities to add useful information.

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 simplicity (1 param, no output schema), the description still fails to cover essential context: what does resetting mean? Is it destructive? Does it produce a new link? Without annotations, 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 description coverage is 100% (parameter 'id' documented as 'Group JID'). The tool description adds no semantic value beyond the schema, so baseline 3 applies.

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 'Reset group invite link' clearly states the action (reset) and the resource (group invite link). It distinguishes well from sibling tools like 'get', 'join', and 'reset_community_invite_link' although it doesn't explicitly mention that it only applies to groups.

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 vs alternatives like getting or joining with a link. It doesn't mention prerequisites (e.g., admin rights) or scenarios (e.g., link compromised).

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