kaiten_delete_column

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core destructive action ('Delete'), but does not reveal important traits such as irreversibility, cascading effects on cards, permission requirements, or whether the operation can fail silently. This is a significant gap for a destructive tool.

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 a single, front-loaded sentence with no filler. It communicates the action and target resource efficiently, and nothing extraneous is included. For a simple two-parameter delete operation, this is appropriately sized.

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?

Although the parameter schema is complete, the description lacks crucial context for a destructive operation: what happens to cards in the column, whether the deletion is permanent, and any permissions or preconditions. With no annotations and no output schema, the description alone does not fully equip an agent to safely invoke this tool.

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 documentation coverage is 100%: both board_id and column_id are described in the schema. The description adds no additional meaning beyond what the schema already provides, so the baseline score of 3 applies. It does not explain relationships between the parameters or any constraints like ownership or visibility.

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 and resource: 'Delete a column from a Kaiten board.' It is specific enough to distinguish from many sibling delete tools like delete_board or delete_workflow, but it does not explicitly differentiate from the closely related kaiten_delete_subcolumn or mention any exclusion criteria.

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 provides no guidance on when to use this tool versus alternatives, nor any prerequisites or consequences that might affect the decision to delete a column. There is no mention of whether the column must be empty, whether deletion is reversible, or when users should prefer listing/updating instead.

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