whatsapp_get_group_info_from_link

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description reinforces it and adds the meaningful side-effect disclosure that no membership is created ('without joining it'). It stops short of describing failure behavior (invalid/expired code, private group) under the open-world hint, so it is good but not exhaustive.

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?

Three short, front-loaded sentences with the scope constraint and the no-join guarantee placed early. 'Returns the group info' is mildly redundant with the field enumeration in the first sentence, a small amount of waste.

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?

With no output schema, the description correctly compensates by naming the returned fields, and it discloses the side-effect boundary. What is missing is only error/edge-case behavior for an open-world fetch, which is a minor gap for a simple one-param read.

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 'code' parameter is documented as 'Invite link code'. The description echoes 'invite code' but adds no format, syntax, or validation detail beyond the schema, so the 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+resource ('Preview a group from an invite code') and immediately clarifies the key distinction from join_group_with_link: 'without joining it.' It also lists the returned fields (name, description, size), so an agent can tell exactly what it gets without opening any schema.

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 phrase 'without joining it' implicitly names the condition that separates this from the join_group_with_link/join_group_with_invite siblings, which is the most likely confusion. It does not explicitly call out an alternative or state when-not to use it, but the contextual routing is clear.

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