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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the side effect that an e-mail is sent to each address and that one invite_url is returned per invitee, plus the owner/moderator permission requirement. It does not cover failure behavior for invalid addresses or partial success.

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 dense sentences: the behavior and modes come first, the return value next, the permission constraint last. Every clause carries a distinct fact.

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, so the description's statement that invite_url is returned per invitee is doing necessary work, and the permission prerequisite is covered. Edge cases such as behavior on invalid e-mails or duplicate invitations are left unaddressed.

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 75% and the description clarifies the semantics of the two optional parameters: emails triggers outbound letters and link produces a universal messenger link, with the "и/или" relationship between them. group_id remains undocumented in either place, which is a minor gap.

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 states a specific verb and resource ("Пригласить участников в форум-группу") and enumerates the two invitation mechanisms plus the return value (invite_url). It clearly differs from the group_create/group_list siblings, though it never names them explicitly.

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?

It explains when each mode applies — e-mail when RuForge should send letters, link when the invite goes to a messenger — and gives the authorization precondition ("Только владелец/модератор группы"). No explicit statement about when not to use it or which sibling to pick instead.

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