sheets_delete_columns

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

Annotations only include idempotentHint; no destructiveHint is provided. The description says 'Delete' but does not disclose consequences such as permanent data removal, shifting of remaining columns, or required permissions. This leaves a significant gap for a mutating 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, front-loaded sentence with a specific verb and resource. It is concise and free of filler, elegantly covering the purpose.

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 tool with two fully described parameters, an idempotency hint, and no output schema, the description covers the essential purpose and scope. It does not discuss side effects, but given the low complexity, the core information is adequate.

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 coverage is 100%, and the parameter descriptions in the schema are already detailed (e.g., range example and spreadsheetId explanation). The tool description adds no extra parameter-level meaning beyond repeating the 'full-column A1 range' concept present in the schema.

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'), resource ('columns from a Google Sheet'), and the specific method ('using a full-column A1 range'). It distinguishes from sibling tools like sheets_delete_rows and sheets_delete_sheet by specifying column deletion.

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 use for deleting columns and emphasizes the full-column range format, but it does not explicitly discuss when to use this tool versus alternatives (e.g., delete_rows, delete_sheet). No exclusions or prerequisites are mentioned.

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