delete_column

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

No annotations are provided, so the description carries full burden. It explicitly discloses the critical behavioral trait — irreversibility — which is the key danger for a delete operation. It could add detail on cascading effects (e.g., whether cards inside the column are also deleted), but the main risk is covered.

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?

Two short clauses with zero waste. The purpose is front-loaded ('Delete a column'), followed by the essential warning. Every word 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 simple 2-parameter delete with full schema coverage and no output schema expectations, the description is reasonably complete. It covers purpose and the destructive nature. The only gap is lack of detail on downstream effects on contained data, which would matter to an agent deciding whether to call it.

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% and both parameters already have clear schema descriptions, so the baseline is 3. The description adds no parameter semantics beyond the schema — it merely echoes 'column' which maps to column_id.

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?

'Delete a column' is a specific verb+resource. The intent is unambiguous, and the resource is clear enough to distinguish from delete_space/delete_board/delete_lane by name, though the description does not explicitly call out sibling differentiation.

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?

No guidance on when to use this tool versus alternatives, no prerequisites (e.g., whether the board must be mutable), and no conditions. The only usage hint is 'confirm with the user,' which is a safety admonition rather than selection guidance.

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