Delete board column

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

With no annotations provided, the description carries the full burden. It discloses that cards move to another column and that the last column cannot be deleted, but fails to specify where cards move (e.g., which column), whether the operation is reversible, or any permissions required. Basic transparency is present but not comprehensive.

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 extremely concise—three short sentences—with no redundant or irrelevant information. Key points are front-loaded, making it easy for an agent to quickly grasp the core function and a critical constraint.

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?

Given no output schema, two parameters, and no annotations, the description provides only foundational context. It explains the basic operation and a constraint, but omits details like what happens to cards (exact destination column), error states, or side effects. It is adequate but leaves gaps for an agent to handle correctly.

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 50% (workspace has a description, column_id does not). The tool description adds no additional meaning for column_id or workspace beyond what is in the schema, leaving the agent without guidance on how to format the column_id or resolve the workspace path. The description does not compensate for the missing schema details.

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 action ('delete') and the resource ('column'), and distinguishes from sibling tools like board_rename_column or board_add_column. The constraint about not deleting the last column adds specificity.

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 mentions a key when-not condition ('Cannot delete the last column'), but does not provide explicit guidance on when to use this tool versus alternatives like board_rename_column or board_move_card. The usage context is implied rather than explicit.

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