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

Annotations already indicate readOnlyHint=false verdict. The description adds useful behavioral context by explicitly disclosing that reset=true revokes the current link and issues a new one, and by requiring the account to be a group admin. This goes beyond the bare structured fields without contradicting them.

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?

Two sentences with no filler. The primary operation is front-loaded, the optional mutation mode is clearly stated, and the key prerequisite is included in a compact final clause.

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 low-complexity tool with a full input schema and an output schema present, the description covers the operation, the reset side effect, and the admin requirement. Nothing essential is missing for an agent to invoke it correctly.

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 every parameter is already documented, including the meaning of reset=true replique. The description adds little beyond restating the reset behavior and the admin requirement. This is the baseline 3 because the schema does the heavy lifting.

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 uses a specific verb ('Get') and resource ('WhatsApp group invite link') and clearly separates the two modes: retrieving the link or setting reset=true to revoke and regenerate it. This uniquely distinguishes it from all siblings, none of which deal with invite links.

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?

The description states the intended use ('Get a WhatsApp group's invite link') and the reset behavior, which is clear context for when to call it. It also notes the group-admin prerequisite. No alternative sibling tool exists for this operation, so explicit exclusions are unnecessary.

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