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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds exactly the context they cannot carry: the login is deleted (sign-in blocked), connected calendars are disconnected, the action is irreversible, and recovery requires re-inviting. It also documents the authorization invariants (owner protected, no self-removal), which are pure behavioral detail.

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?

Four sentences, all load-bearing: consequence, irreversibility, invariants, and the required confirmation protocol. The destructive scope is front-loaded with 'PERMANENTLY', so an agent knows the stakes before reading further.

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 an output schema present, return values need no explanation; the description instead covers everything that matters for a destructive two-param operation: source of the ID, side effects, irreversibility, blockers, and the mandated confirmation dialogue. Nothing an agent needs to call this safely is missing.

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%, so the baseline is 3; the description meaningfully raises it by tying teamMemberId to list_team_members as its source and by spelling out the conversational confirmation flow that makes confirm: true valid. It stops short of adding format or edge-case detail beyond that.

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 ('PERMANENTLY removes a team member') plus scope ('from the connected Nexwin account'), and names the source of the ID (list_team_members). It is unambiguously distinguishable from siblings add_team_member, invite_team_member and update_team_member without opening any 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?

Explicitly states preconditions and prohibitions: the account owner cannot be removed, nobody can remove themselves, and the call requires telling the user who will be removed and getting an explicit yes before passing confirm: true. It also points to list_team_members as the way to obtain teamMemberId, so the agent has a full operational path.

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