whatsapp_get_group_invite_link

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

Annotations only declare that this is a read-only, open-world call. The description adds material behavior beyond that: the admin-rights requirement (authorization) and the security implication that anyone holding the link can join, plus confirmation of the 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?

Four short sentences, all front-loaded and free of filler; the admin requirement and security caveat are placed early. The closing 'Returns the link' is mild restatement of the first sentence but not wasteful.

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 simple read-only getter with a single fully documented parameter and no output schema, the description covers the essentials: what it returns, the authorization requirement, and the join-security implication. Nothing critical is missing, though an explicit note on where to use the returned link would be a bonus.

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?

Only one parameter ('id', Group JID) and the schema already documents it with 100% coverage, so the baseline is 3. The description adds nothing about the id format or which group identifier to pass.

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?

States a specific verb and resource ('Get the current invite link of a group'), and the word 'current' implicitly separates it from the sibling whatsapp_reset_group_invite_link. It stops short of explicitly naming that alternative, so it is clear but not maximally differentiating.

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?

Provides one precondition ('Requires admin rights'), which is useful context for deciding whether the call can succeed. However, it gives no guidance on when to prefer this over resetting the link or fetching group info from a link, leaving the routing decision implied.

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