Delete Columns

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

The annotations already flag this as destructive (destructiveHint=true). The description adds useful context by stating that columns to the right shift left and that a JSON confirmation is returned, but it does not go further into irreversibility, formula/reference impact, or how deleted cell contents are handled.

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 compact and front-loaded with the core behavior before the Args section. Every sentence contributes meaning, and the parameter list is cleanly structured without unnecessary filler.

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 tool is straightforward and the description covers behavior, parameters, and return value. It would be slightly more complete if it resolved the mismatch between the claimed required column parameter and the schema's optional flags, and if it warned about permanent data loss, though destructiveHint partially covers that.

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?

With 0% schema description coverage, the description takes on the burden of explaining all parameters and does so well: workbook/sheet active defaults, column letters, and count. The only caveat is that 'column (required)' conflicts with the schema's lack of a required field, which could cause slight ambiguity.

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 a specific verb and resource: 'Delete one or more columns, shifting columns to their right left.' This clearly distinguishes the tool from siblings like delete_rows, delete_worksheet, and delete_table by naming columns as the exact target.

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 clearly establishes when to use this tool: when deleting columns from a worksheet. It does not explicitly name alternatives or exclusions, but the column-specific language and count parameter make the intended use obvious among the many sibling tools.

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