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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnly=false, so the safety profile is covered. The description nonetheless adds substantive context beyond them: it clarifies what survives (conversations stay) and what is destroyed (access is lost), which is exactly the kind of consequence detail annotations cannot convey.

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, front-loaded with the action and followed immediately by the consequence. No filler, no restatement of the title.

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 one-parameter destructive mutation whose annotations carry the safety profile and which has no output schema, the description supplies the key missing piece — what remains after removal. Only the parameter itself is left undocumented, which is a minor omission for a single required integer ID.

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% and the description never names or describes agent_id — it only says 'a person from this account'. With a single required parameter the gap is small in practice, but the description does not compensate for the undocumented schema field at all.

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 a person from this account'), which is clear and concrete. However it doesn't distinguish itself from close siblings like remove_inbox_member and remove_team_member — the 'from this account' phrasing implies scope but never contrasts with those membership-removal tools.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. With three 'remove_*' siblings in the list, the description leaves the agent to infer that this removes the person from the account entirely rather than from an inbox or team.

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