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

Annotations already declare this is a non-idempotent, open-world write with destructiveHint=true; the description adds genuine context beyond them: placement at the top of the Unsorted panel, that the returned column_id is the handle for move_card, and the visibility/notification behavior ('Editors of the board see it, nobody is notified'). It does not reconcile why the operation is flagged destructive (e.g., whether it displaces or affects existing columns), leaving a small gap.

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 dense sentences with the core action and placement front-loaded, and no filler. The opening fragment ('Empty column on a board, to group cards in a stack') slightly overlaps with the sentence that follows, a minor redundancy.

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?

No output schema exists, and the description compensates by naming the return value (column_id) and its downstream use. Placement, visibility, and notification are covered; missing only error/permission specifics and the effect on existing column ordering.

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 100%, so both parameters are already documented, including that board_id accepts a board URL. The description adds placement semantics but nothing about title constraints or board_id sourcing beyond what the schema states, so it sits at the baseline.

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 concrete verb and resource ('Adds a titled column') plus precise placement ('on top of the board's Unsorted panel'), which no sibling tool does. An agent can distinguish it immediately from create_board, move_card, or add_note.

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?

Usage is implied through the follow-up hint that move_card with to_column_id puts cards into the new column, which tells the agent the natural next step. However, there is no explicit when-to-use or when-not framing versus alternatives (e.g., existing columns, other board-structuring tools) and no stated preconditions.

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