delete_rows

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

With no annotations, the description carries the full burden. It discloses destructive behavior, the dry_run safety default, and that rows are snapshotted before deletion. It also mentions the force parameter. Missing details on where snapshots go or irreversibility, but overall strong.

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?

Description is compact and front-loaded with the key point: 'Delete rows (destructive — dry_run defaults to TRUE).' Each subsequent sentence adds necessary detail without redundancy. No wasted words.

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?

Given the tool's complexity (6 params, destructive), no annotations, and no output schema, the description covers all parameters and behavioral effects (snapshot, dry_run, force). It does not explain return values, but that is not critical. Could mention where snapshots are stored, but otherwise complete.

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 has 0% description coverage, but the description provides detailed meaning for all six parameters, including defaults and types (e.g., '1-indexed first row', 'Full Sheets URL or bare spreadsheet ID'). This fully compensates for schema gaps.

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 rows' and the resource, and implies it is destructive. It provides specifics like snapshotting, which distinguishes it from clear_range. However, it does not explicitly differentiate from sibling tools such as delete_columns or delete_sheet, leaving some ambiguity.

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 mentions that dry_run defaults to TRUE, implying a safe preview mode, but does not provide explicit guidance on when to use this tool versus alternatives like clear_range or delete_sheet. No when-not-to-use or alternatives are listed.

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