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

With no annotations, the description carries the full burden and delivers: it discloses the side effect of reverting a member to a regular Telegram member on group-linked boards, the no-op case for Telegram-only members, and the permission hierarchy. It doesn't cover notifications or return behavior, but the mutation's key traits are well surfaced.

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?

The purpose is front-loaded in the first sentence and each subsequent sentence adds a distinct constraint (revert behavior, removability, permission rules). The text is dense but every sentence earns its place; no filler.

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 two-parameter mutation with no output schema, the description covers who may call it, what happens to the target, and the failure case comprehensively. Return/confirmation behavior is not described, but the permission and side-effect picture is essentially 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 100% and both parameters (board_id, user_id) are already documented in the schema. The description adds no syntax or format meaning beyond what the schema provides, so the baseline 3 applies.

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 opens with a specific verb+resource ('remove a member from a board') that immediately distinguishes it from siblings like add_board_member and invite_board_member. An agent can tell exactly what this does 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 clearly specifies who can perform the removal (owner removes admin/user, admin removes user) and the exclusions ('Cannot remove owner'), plus the edge case that Telegram-only members cannot be removed. It lacks an explicit comparison against sibling removal/role tools, but the conditions are well stated.

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