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 destructive behavior (deletes column and contained cards) and the safeguard that the last column remains. It does not mention permissions or irreversibility, but the core effects are clear.

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 concise sentences, each providing essential information. No filler or redundancy, and the main action is front-loaded.

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 deletion tool with two parameters, the description covers the main action, associated card deletion, and the last-column rule. Missing details like return value or error handling are not critical given the tool's simplicity and lack of output schema.

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 only 50% (column is described, board_id is not), and the description does not compensate. It adds no parameter-level guidance beyond what the schema already provides, missing the opportunity to explain board_id or relationships.

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 tool deletes a column and all cards within it, using the verb 'delete' and the resource 'column'. The additional note that the last column remains adds scope clarity, distinguishing it from sibling tools like delete_card or delete_board.

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 implies usage for deleting columns and notes the last-column limitation, but it does not explicitly mention when to prefer this tool over alternatives such as delete_card or add_column. The constraint is useful but not framed as usage guidance.

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