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

Annotations only declare readOnlyHint false, implying mutation, but the description adds meaningful behavior: it explains that with member_id the invitee becomes a named placeholder preserving history, otherwise they join as a new member. This goes beyond annotations and discloses the key side effect of creating an invite link, though it does not mention expiration or other potential side effects.

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 with no filler. The core purpose is stated first, followed by the conditional behavior. Every word earns its place, and the structure is front-loaded.

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?

Given the tool's simplicity, the description covers the two operating modes and their outcomes. An output schema exists, so return values are defined elsewhere. Minor gaps like prerequisites or invite-link lifecycle are not critical for a straightforward tool like this.

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 0%, so the description must compensate. It explicitly explains the meaning of member_id and its two states. group_id is not directly described, but its purpose is obvious from the context and title. The description adds value for member_id but leaves group_id to inference.

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 clearly states the tool creates an invite link for a group and distinguishes two modes based on member_id. This is specific enough to differentiate from sibling tools like add_group_member, which adds members directly, and the title reinforces the action.

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 description provides clear guidance on when to use member_id (to assign a placeholder) versus not (to add a new member). However, it does not explicitly mention when to choose this tool over alternatives like add_group_member or settle_group, though the invite-link concept implies a different use case.

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