delete_column

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral constraint ('Cannot delete read-only or sealed columns'), which is valuable context beyond the basic 'delete' action. However, it doesn't cover other important traits like permissions needed, whether the deletion is reversible, error handling, or what happens to data in the column. It adds some value but leaves gaps for a mutation tool.

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 a single, efficient sentence with zero waste. It front-loads the core action and immediately adds the critical constraint. Every word earns its place, making it easy to parse quickly without unnecessary elaboration.

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 this is a mutation tool with no annotations, 0% schema coverage, and no output schema, the description is moderately complete. It covers the purpose and a key constraint, but lacks details on parameters, return values, error cases, or side effects. For a destructive operation, more behavioral context would be helpful, but it meets a baseline for a simple tool.

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%, so the schema provides no parameter details. The description adds minimal semantics by specifying 'by internal name', which clarifies that 'internalName' refers to the column's internal identifier, not display name. However, it doesn't explain 'listName' or provide format examples. It partially compensates for the coverage gap but doesn't fully document both parameters.

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 action ('Delete') and target resource ('a column from a list'), specifying it's done 'by internal name'. It distinguishes from siblings like 'delete_item' or 'delete_list' by focusing on columns, but doesn't explicitly contrast with 'update_column' which might be a closer alternative. The purpose is specific but could better differentiate from similar operations.

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 provides some implicit guidance by stating 'Cannot delete read-only or sealed columns', which hints at when NOT to use this tool. However, it doesn't explicitly say when to use it versus alternatives like 'update_column' for modifying columns or 'delete_list' for entire lists. The context is clear but lacks explicit when-to-use or alternative tool references.

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