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

Annotations already flag destructiveHint=true, but the description goes well beyond them by enumerating exactly what is destroyed (access, assignments, watches, reactions) and what is preserved (comments). It also discloses the safe-preview mode when confirm is absent, which is precisely the kind of behavioral context an agent needs before a destructive call.

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 compact sentences with the effects front-loaded and the confirm/preview rule second; no filler, no restatement of the title, and every clause carries information the agent needs.

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 three-parameter destructive mutation with no output schema, the description covers effects, side effects, and the preview return behavior adequately. It omits error/edge cases (e.g., what happens when the user is not a member), which keeps it short of 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 coverage is 33% (only confirm is documented), and the description repeats the schema's preview wording rather than adding new syntax. boardId and userId are self-describing names, and the 'board the user owns' note implies required ownership of boardId, so the gap is modest but real.

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 ('Removes someone from a board') and scopes it with a precondition ('the user owns'), which helps separate it from siblings like leave_board (self-removal) and revoke_access. It does not explicitly name or rule out any sibling, so it stops short of a 5.

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?

Gives a clear usage condition (only for boards the user owns) and a required invocation mode ('Needs confirm: true'), which prevents accidental mutation. It does not say when to prefer a different tool or what happens if the target is not a member, so no exclusion guidance is present.

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