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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds real value beyond them: the side effect that the current owner is demoted (default 'admin'), the authorization requirement (caller must be the owner), and an explicit irreversibility warning. It stops short of describing failure modes (e.g., invalid target ID, insufficient permissions) or whether the new owner can transfer back.

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?

Four tight sentences, zero filler, with the core action stated first and constraints and the irreversibility warning following in priority order. Every sentence contributes a distinct fact an agent needs to act correctly.

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 3-parameter mutation with full schema coverage and destructive annotations, nothing critical is missing: actor requirement, target precondition, side effect, default, and irreversibility are all stated. No output schema exists, and return values would be minimal for a transfer confirmation, so the description carries enough.

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% and each parameter is already documented in the schema, including the 'defaults to admin' behavior and the board-member constraint on to_user_id. The description restates these constraints rather than adding syntax, format, or edge-case meaning, 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?

States a specific verb and resource ('Transfer ownership of a board') plus the exact endpoints of the transfer (current owner → existing admin/user member), which distinguishes it from siblings like update_member_role or invite_board_member. The scope of who may be a target is stated inline, so an agent can identify the tool 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?

Gives clear preconditions: 'Only the current board owner can initiate a transfer' and 'The target must already be a board member — invite them first if needed', which routes the agent to invite_board_member when the precondition fails. No explicit when-not-to-use guidance (e.g., use update_board to change other settings, or update_member_role for non-ownership role changes) is provided.

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