Delete board 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 merely states 'Delete board column' without disclosing behavioral traits such as reversibility, permissions, cascading effects, or idempotency. This is insufficient for an agent.

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 very short but includes redundant information: the HTTP method and route ('DELETE /tm/board-columns/{id}') are unnecessary for an AI agent. The tag line 'Tags: BoardColumn' adds no value. Could be trimmed to a single sentence.

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 the simple operation and lack of output schema, the description is minimal. It does not explain what a board column is, that it must exist, or how the id relates to other tools. Sibling tools provide some context, but the description itself is incomplete.

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?

The input schema has one nested parameter 'id' with zero description coverage in both schema and tool description. The description does not explain what 'id' represents or how to obtain it, providing no value beyond the schema structure.

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 uses the verb 'Delete' and resource 'board column', clearly indicating the action. It distinguishes from siblings like 'create_board_column' and 'update_board_column'. However, it offers no additional context beyond the name and title.

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 is provided on when to use this tool versus alternatives such as 'delete_board' or other delete operations. There is no mention of prerequisites like column existence or contents.

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