delete_columns

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

The description states a destructive action (delete) but provides no additional behavioral context such as that the deletion is irreversible, requires a valid session_id, or modifies the sheet permanently. With no annotations, the description should explain side effects, but it only gives the basic 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 a single sentence that is front-loaded and efficient, containing no redundant words. It could be slightly expanded to include more detail without losing conciseness, but as a minimal viable description it earns a 4.

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 destructive tool with 4 parameters and no output schema, the description lacks key context: it does not mention the count parameter (which controls how many columns to delete), the optional sheet parameter, or that the effect is limited to columns starting at the given one and moving right. This leaves gaps for correct invocation.

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 adds useful meaning to the 'column' parameter by noting it can be a letter ('B') or 1-based index. However, the count, sheet, and session_id parameters are not described. Since schema coverage is 0%, the description partially compensates for one parameter, leaving others ambiguous.

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 columns starting at a given column, using a verb and resource. It distinguishes from siblings like delete_rows and delete_sheet by specifying 'columns'. However, it does not specify the direction of deletion (to the right) or whether the starting column itself is included, which could cause confusion.

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 like delete_rows or insert_columns. It does not mention that the count parameter defaults to 1 or that only columns from the starting point onward are affected. An agent would need to infer usage from the name alone.

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