delete_column

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

With no annotations, the description carries the full burden. It discloses the most important consequence (cards return to the default/uncategorized column), which is strong for a destructive tool. It does not state irreversibility, permission requirements, or response/error behavior, leaving some gaps.

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 sentences with the core action front-loaded and the key side effect second. There is no filler or repetition, so 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 simple delete operation, this is largely complete: purpose, required entity, and the main side effect are all present. It would be more complete with explicit permissions/irreversibility or return-value guidance, but an agent can select and invoke the tool correctly from this definition.

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 0%, and the description provides no parameter-specific guidance beyond referring to 'a column.' The parameter names owner, repo, project_id, and column_id are somewhat self-explanatory, but the description fails to compensate for the missing schema documentation.

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 precise action and resource ('Delete a column') and immediately adds a distinguishing behavioral detail: cards are not lost but moved to default/uncategorized. This distinguishes it from edit_column, delete_project, and move_card.

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 intended use is implied: call this when a column should be removed. The card-relocation sentence gives useful context for deciding whether it is appropriate, but it does not explicitly contrast with alternatives such as edit_column or delete_project, nor state when not to use it.

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