update_board_member

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

No annotations are provided, so the description carries the full burden. It does disclose one real behavioral requirement — that confirm must be true — which the agent would not know from the schema default of false. It omits permission requirements (likely admin/owner), whether a role change is reversible, and side effects such as loss of access for the demoted member.

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; the scope and the allowed values come first and the hard prerequisite follows. 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?

An output schema exists, so return values need not be described, but this is a privilege-mutating operation with zero annotations and no statement of authorization requirements or consequences. For a write tool that can strip a member's access, that is a meaningful gap.

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 0%, so the description must compensate for four undocumented parameters. It clarifies only 'confirm' (must be true) and restates the role enum already present in the schema; board_id and member_id — the identifiers that determine which membership is mutated — get no explanation of format or source.

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 ('Change a board member's role') and enumerates the valid roles. It is distinguishable from siblings like get_board_member, list_board_members and remove_board_member by the verb, though it never names them explicitly.

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 'Requires confirm=true' line gives a concrete invocation prerequisite, which is more than implied usage. But there is no guidance on when to use this versus remove_board_member (to revoke) or who is permitted to call it.

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