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

Far beyond the annotations: it discloses that old invite links stay valid, that revoke/pin/unpin mutate state, that unban leaves the user 'left' and they must rejoin, and that post-unmute status reads 'restricted' even though all can_send_* are true. It also flags the hard limitation that a bot cannot add members or create groups at all, which is exactly the kind of surprise a caller needs.

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?

Front-loaded with the purpose, then a scannable action list, then caveats, then the return shape. Every bullet carries concrete information, though the density of caveats makes it on the long side for a tool an agent must parse on every call.

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 closes the loop by naming the returned keys (invite_link, admins, member_count, status, result). It is complete for correct invocation, but the missing steer away from the narrower sibling moderation tools leaves a tool-selection gap.

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% for the five top-level params, so the baseline would be 3; but the description carries meaning the schema cannot, since `action` has no enum and the schema only says 'see the tool description'. The bullet list supplies every valid action value and its action-specific `params` keys (user_id, message_id, title, rights, revoke_messages, until_date, member_limit, expire_date).

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 names a specific verb+resource ('Run ONE moderation action on a group the connected account administers') and enumerates every supported action with its parameters, so the scope is unambiguous. It does not, however, differentiate itself from overlapping siblings such as group_promote_admin, group_admins, and group_get_invite_link, which cover a subset of the same actions.

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 gives real preconditions per action, e.g. 'Check `can_be_edited` in member_status first' and 'promote additionally needs the bot to hold can_promote_members', which tells the agent when an action will fail. It never states when to choose this dispatcher over the narrower sibling tools, so the alternative-selection guidance is absent.

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