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 demotion side effect on the current owner, the default role, the permission requirement, the target precondition, and flags irreversibility ('irreversible high-impact operation'). This is exactly the behavioral context annotations would otherwise supply.

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?

Front-loads the core action, then layers preconditions and the irreversibility warning in tight, waste-free sentences. No filler or redundancy despite covering several distinct facts.

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 high-impact mutation with no annotations and no output schema, the description covers prerequisites, side effects, defaults, and irreversibility. Nothing an agent needs before calling is missing.

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 100%, so all three parameters (including the demote enum and its 'admin' default) are already fully documented. The description restates the demotion default and target-membership rule but adds no syntax, format, or meaning beyond the schema. 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?

States a specific verb and resource ('Transfer ownership of a board') plus the exact source and target actors. It is clearly distinguishable from sibling member tools like update_member_role, add_board_member, and invite_board_member.

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 explicit preconditions ('Only the current board owner can initiate a transfer'), a constraint on the target ('must already be a board member'), and names the corrective alternative ('invite them first if needed'). An agent has everything needed to decide whether and how to call it.

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