delete_range

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

The destructiveHint annotation already signals the destructive nature, and the description adds the useful detail that remaining cells are shifted after deletion. However, it does not disclose the impact on formulas, formatting, merged cells, or default shift direction. Given the annotation covers the core destructive trait, the added value is moderate but not extensive.

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, compact sentence that efficiently conveys the core operation. No fluff or redundancy; it is front-loaded with the verb and object.

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 six parameters, no output schema, and meaningful optional parameters (dry_run, shift_direction), the description is too sparse. It omits return behavior, error conditions, and the existence of dry_run for safe previewing, leaving significant gaps for an agent.

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 schema has 0% description coverage, so the description is the sole source of parameter meaning. It only loosely implies start_cell/end_cell with 'range' and shift_direction with 'shift', but does not explain any parameter names, value formats (e.g., 'A1:B2'), defaults, or the dry_run safety flag. This is insufficient for an agent to correctly populate all six 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), the target (a range of cells), and the subsequent behavior (shift remaining cells). This distinguishes it from sibling tools like delete_sheet_rows/delete_sheet_columns, which target entire rows/columns, and delete_worksheet, which removes a whole sheet.

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 no guidance on when to use this tool versus alternatives. It does not mention scenarios where range deletion is preferred over deleting entire rows/columns, nor any prerequisites or conditions that would make this tool the right choice.

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