Delete column

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

With no annotations at all, the description carries the full burden of behavioral disclosure. It explicitly states the operation is permanent, describes the column-shifting side effect, lists refusal conditions (built-in and missing columns), and mentions the backup to .bak. This is exemplary transparency for a destructive operation.

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 three sentences, each providing distinct value: purpose and behavior, failure conditions, and safety backup. No unnecessary words or repetition, and it is front-loaded with the core action.

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 single-parameter tool with no output schema, the description comprehensively covers what the tool does, how it affects the data, when it refuses, and what safety measure is taken. It is complete without being verbose.

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 100% coverage for the single 'name' parameter, which is already described as 'Header text of the column to delete.' The description adds no additional parameter-level meaning beyond 'custom column' in the purpose, so the baseline of 3 is appropriate.

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 'permanently remove a custom column' and describes the specific behavior of shifting columns to the right left by one, using the Excel analogy for immediate understanding. This distinguishes it from sibling tools like add_column or modify_column.

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 through the Excel analogy and notes it refuses on built-in columns, but it does not explicitly state when to use this tool versus alternatives like modify_column or add_column. No direct when-not-to-use guidance beyond built-in columns is provided.

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