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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds one genuinely new behavioral fact — 'Returns join links' — but says nothing about result volume, link freshness, or empty-result handling, so it is useful but not rich.

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, front-loaded with what the tool returns and followed by the usage trigger; nothing is wasted. The parenthetical city list is long but each entry maps directly to the coverage claim, so it earns its space.

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?

No output schema exists, and the description compensates by stating that join links are returned. Combined with the geographic and academic-year scope and the usage trigger, an agent has what it needs to call this 0-required-parameter tool correctly; only result-set characteristics remain unspecified.

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 description coverage is 100%, so city, country and lang are already documented in the schema with examples and defaults. The description's city/country enumeration mirrors the schema rather than adding format or matching semantics, so the baseline 3 is correct.

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 ('Find') and resource ('WhatsApp groups') with precise scope: Erasmus/exchange students heading to South America in 2027, listing both countries and cities. This is instantly distinguishable from the travel/accommodation siblings, none of which concern student communities.

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 second sentence gives an explicit trigger ('Use when a student asks for a WhatsApp group, community or other exchange students in these places') and extends coverage to the 2026/27 and 2027/28 academic years. No when-not condition or named alternative is offered, but the sibling set is so dissimilar that overlap risk is minimal.

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