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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds the useful scoping fact that permanent removal is out of scope here, but says nothing about reversibility of deactivate/revoke or what happens on re-invite.

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 tight sentences, front-loaded with the action list and closing with the sibling routing rule. Nothing is padded and every clause carries 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 7-parameter, 7-action mutation tool with no output schema and zero schema descriptions, the description is materially incomplete. The action-to-parameter mapping and per-action preconditions are the core missing content an agent needs to call this correctly.

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 description carries the full burden, yet it only says 'set `action` accordingly'. With 7 parameters (membershipId, invitationId, email, role, accountType, invitations) it never explains which fields pair with which action, e.g. that bulk_invite needs the invitations array or that update_role needs membershipId plus role.

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 enumerates the specific operations (invite, re-invite, revoke, deactivate, change role, send reminder) against a named resource, and explicitly distinguishes itself from the remove_member sibling. An agent can tell what this tool does and does not do without opening the schema.

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 an explicit when-not rule: full removal belongs to remove_member, which stays separate. It also tells the caller to drive behavior via `action`. What it lacks is any guidance on which parameters each action requires, so the caller still has to infer usage per action.

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