whatsapp_get_community_invite_link

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

Annotations already establish this as a read-only, open-world call, so the bar is lower; the description still adds real value by disclosing the admin-rights requirement and the security implication that anyone holding the link can request to join. It stops short of covering failure modes (e.g., what happens if no link exists) or return format.

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 with the action front-loaded and no filler. 'Returns the link' is mildly redundant with the opening sentence but also confirms the output in the absence of an output schema, so it roughly earns its place.

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 one-parameter, read-only lookup with no output schema, the description covers purpose, permission requirement, and the nature of the returned value. Adequate; only edge-case behavior and JID sourcing are left implicit.

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% and the single parameter 'id' is documented as a Community JID, so the schema carries the load. The description adds no syntax, format, or source guidance for obtaining that JID; 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?

States a specific verb and resource (get the current invite link of a community), which clearly separates it from group/chat tools. It does not, however, explicitly name the nearest sibling (whatsapp_get_group_invite_link) or clarify the community-vs-group distinction for an agent scanning a long sibling list.

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 a prerequisite ('Requires admin rights') but no when-to-use guidance relative to alternatives such as whatsapp_reset_community_invite_link or the group equivalents. Usage is implied rather than stated.

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