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

With no annotations, the description carries the full burden and does disclose two meaningful side effects: the task gets a new number in the target board, and status is reset to the target board's default when the current status doesn't exist there. It does not disclose what happens to the source-board number, whether comments/checklists/history carry over, or any permission requirements, which keeps it out of 5 territory.

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?

Three short sentences, zero filler, front-loaded with the action and followed immediately by the two behavioral consequences an agent needs before invoking. Every sentence earns its place.

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 three-parameter mutation tool with no annotations and no output schema, the description covers the essential behavioral surprises (renumbering, status reset). It is not fully complete — transfer semantics for related data and failure conditions (e.g., invalid target board) go unmentioned — but nothing critical is missing for a correct call.

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 task_number, source_board_id, and target_board_id are already fully documented in the schema. The description adds no syntax, format, or constraint detail beyond it, 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 states a specific verb and resource ('transfer a task between boards'), which distinguishes it from update_task (field edits), transition_task_status (status-only change), and move_board (moving a board, not a task). It never names a sibling explicitly, so it stops short of a 5, but the resource scope is unambiguous.

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?

'Use this to transfer a task between boards' implies the context of use but names no alternative and no exclusion — an agent is left to infer that this is the cross-board move path rather than transition_task_status or update_task. Adequate but with a clear routing gap in a sibling list that contains three other task-mutating tools.

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