Change member role

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

Annotations already indicate a mutating, destructive operation, so the description doesn't need to restate that. It adds valuable context by specifying the required authorization level (ADMIN/OWNER), which is critical for an agent to know before invoking. This goes beyond the structured annotations.

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 description is a single, efficient sentence that front-loads the purpose and includes the key requirement. No unnecessary words, making it highly concise and clear.

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?

The description omits critical context about how to identify the target board. The schema does not require board_id or board_slug, yet the description says 'on that board,' leaving ambiguity about whether board identification is needed and how it should be provided. This is a meaningful gap for correct invocation.

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?

The input schema provides 100% coverage with descriptions for all parameters, so the description does not need to compensate. It does align 'role/title' with the role and title params, but adds no additional meaning beyond what the schema already offers.

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 clearly states the tool's function with a specific verb and resource: 'Update board member role/title.' This distinguishes it from sibling tools like remove_board_member and list_board_members, which handle deletion and listing, making the purpose unmistakable.

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 description provides a clear permission prerequisite ('Requires ADMIN/OWNER on that board'), which is a useful usage constraint. However, it does not explicitly contrast with alternatives (e.g., remove_board_member for removal) or state when not to use it, leaving some ambiguity.

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