whatsapp_get_community_invite_link

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

With no annotations provided, the description fully bears the burden of disclosing behavioral traits. It does not specify that this is a read-only operation, that it requires an existing community, or that it may fail if the community has no invite link. No mention of permissions, rate limits, or error conditions.

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 concise—only six words with one verb and one noun. While it is short and front-loaded, it could be slightly more informative without adding significant length (e.g., 'Returns the current invite link for the community with the given JID'). However, it is not verbose and earns a 4.

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 absence of an output schema, the description should at least mention what the tool returns (e.g., the invite link string). It also lacks context on how the returned link differs from reset links or how to use it. For a simple tool, it is functional but incomplete.

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?

The input schema has 100% description coverage for the single parameter 'id' (Community JID), so the description adds no extra meaning. According to the rubric, the baseline is 3 when coverage is high, and the description does not provide additional clarification beyond the schema.

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 clearly states the action ('Get') and the resource ('community invite link'), making the purpose immediately understandable. It distinguishes from sibling tools like 'whatsapp_get_group_invite_link' by specifying 'community'. However, it could be slightly more precise by indicating that it returns the invite link, but the current phrasing is adequate.

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 provides no guidance on when to use this tool versus alternatives such as 'whatsapp_reset_community_invite_link' or 'whatsapp_join_group_with_invite'. It also does not mention prerequisites (e.g., admin privileges) or context for using the returned link.

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