whatsapp_reset_community_invite_link

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

With no annotations provided, the description carries full burden but only says 'reset', which implies a destructive or modifying action. It does not disclose side effects, permissions required, or whether the operation is reversible. This is insufficient for safe invocation.

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 extremely short (three words), but it fails to add value beyond the tool name. It is under-specified rather than concise, as every sentence should contribute new 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 complexity of resetting an invite link (side effects, permissions, return values) and the absence of annotations and output schema, the description is completely inadequate. It provides no context about what the action does beyond the name.

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%; the single parameter 'id' is described as 'Community JID' in the schema. The tool description adds no additional meaning, but the schema already adequately documents the parameter. Baseline of 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 community invite link' simply restates the tool name without adding specific verb-resource details or differentiating from the sibling tool 'whatsapp_reset_group_invite_link'. It lacks clarity on what 'reset' precisely entails (e.g., invalidates old link, generates new one).

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 on when to use this tool versus alternatives like 'whatsapp_get_community_invite_link' or 'whatsapp_reset_group_invite_link'. Prerequisites (e.g., admin permissions) are not mentioned.

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