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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds a genuine behavioral detail beyond the annotations — that removal requires explicit confirmation — and clarifies self-scope via 'connected user.' It does not, however, disclose consequences such as whether the last admin can leave or what happens to resources they own.

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?

A single front-loaded sentence with no padding; the destructive action and its condition come first. It is efficient, though arguably terse enough that it leaves gaps that a slightly longer description could have closed.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. Still, for a destructive, self-removal team operation the description omits permission requirements, edge cases (e.g., sole owner leaving), and any coupling to team membership state, leaving it only minimally complete.

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 must carry parameter meaning. It indirectly explains `confirmed` via 'explicit confirmation,' but never names or explains `teamId`, and its two-sentence scope is too thin to compensate for the complete lack of schema documentation.

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 ('Remove ... from a team') and narrows the scope with 'the connected user,' which distinguishes it from the sibling remove_team_member that acts on other users. It stops short of explicitly naming that sibling as the alternative, so it is clear but not fully differentiated in-text.

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 'after explicit confirmation' functions as a precondition, implying the tool should only be called once the user has agreed. However, it gives no when-to-use vs alternatives guidance and never contrasts itself with remove_team_member, delete_team, or revoke_team_invite, leaving the agent to infer routing.

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