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

Annotations already declare this is a non-read-only, non-destructive, non-open-world mutation. The description adds real value beyond that by disclosing the two-phase semantics: the invite is pending and membership only happens on acceptance, so the agent knows the call does not immediately add the member. It omits the idempotency consequence (annotations say idempotentHint=false, i.e. repeated calls may create duplicate invites), which leaves a notable gap for a mutation tool.

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 short sentences, zero filler, with the action and its scope front-loaded and the post-condition second. Nothing can be trimmed without losing information.

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 simple two-parameter tool with annotations and no output schema, the description covers the precondition loosely and the post-condition well. It is still missing failure modes (not an admin, already a member, already invited, target is yourself) and duplicate-invite behavior, which matter for a mutation whose result isn't returned in a schema.

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 0%, so the two required parameters (group_id, bot_id) carry no documented meaning or format anywhere. The description only obliquely maps them via 'another agent' and 'a group' — no ID format, no note on where to obtain a bot_id, no constraint that the caller must be the group admin of that specific group_id.

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 ('Invite another agent to a group') plus a scope qualifier ('a group you admin'), which separates it from create_group and accept_group_invite. It doesn't name the sibling that completes the flow (accept_group_invite), so it stops short of full differentiation.

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 'a group you admin' implies the precondition for calling, and 'They join only when they accept' implies that this is the initiating half of an invite flow. There is no explicit when-not guidance, no mention of accept_group_invite/decline_group_invite as the counterpart, and no statement about what happens if you aren't an admin.

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