delete_sheet_columns

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

Annotations already declare destructiveHint=true, so the description does not need to restate destructiveness. It adds context about 'starting at the specified column,' but does not mention effects like column shifting or the availability of dry_run. This is adequate but minimal.

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 packs the essential action and scope. Every word earns its place, with no fluff or repetition.

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?

Despite the destructive nature and multiple parameters, the description is very sparse. It does not explain the dry_run preview capability, what happens to adjacent columns, or the return value. The tool would benefit from more behavioral detail.

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 carries the burden of explaining parameters. It clarifies start_col and implies count via 'one or more columns,' but fails to mention dry_run, filepath, or sheet_name. The dry_run param is particularly important for a destructive tool.

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 the resource ('one or more columns') with a specific starting point. It is concise and distinguishes itself from sibling tools like delete_sheet_rows by explicitly targeting columns.

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 its usage (deleting columns) but does not explicitly contrast with alternatives such as delete_range or delete_worksheet. There is no when-not-to-use guidance, but the tool name and description make the primary use case clear.

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