delete_column

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

The description explicitly warns that the operation is destructive and advises confirming with the user first, adding context beyond the destructiveHint annotation. It also clarifies the scope (deletes every value stored in the column), which is valuable behavioral transparency.

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 deliver all necessary information without redundancy. It is well-structured, front-loading the core action and then adding critical caveats (destructive, confirm, alternative tool).

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?

The description covers the essential context: what the tool does, its destructive nature, user confirmation, and when to avoid it. It does not mention potential cascading effects or dependencies on column references, but given the simplicity of the deletion operation and the absence of an output schema, this is sufficiently complete.

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 description does not add any parameter-specific meaning beyond the schema. However, since the schema itself has 100% coverage for all three parameters (projectId, boardId, columnId), the description's lack of additional per-parameter details is acceptable and aligns with the baseline.

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?

Clearly states the action (delete a column) and the resource (column), and explicitly mentions that it removes all values stored in it. It also distinguishes itself from update_column, making its purpose unambiguous.

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?

Provides explicit guidance on when to use this tool (deleting a column) and when to use the alternative update_column (when the column is right but name/type/options are wrong). This directly helps the agent choose correctly.

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