delete_rows

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

No annotations are provided, so the description must disclose behavior. It describes the parameters but does not mention any side effects (e.g., shifting rows, inability to undo, or restrictions like deleting all rows). The description is minimal beyond the obvious deletion action.

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 concise and structured with an 'Args' block, listing parameters clearly. It front-loads the primary action. The format is efficient, though slightly unnatural for natural language understanding.

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 an output schema, the description is adequate but incomplete. It lacks mention of row shifting, undo behavior, or constraints (e.g., cannot delete all rows). The presence of siblings like delete_columns suggests a pattern, but the description does not leverage that context.

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 compensates by explaining each parameter: sheet index (0-based), row (1-based), and count (default 1). This adds meaning beyond the schema's type information, though it does not clarify boundary behavior (e.g., what happens if count exceeds available rows).

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 (starting at a given position in a sheet). It distinguishes from siblings like delete_columns and delete_sheet by specifying rows. However, it does not explicitly differentiate from other row operations like insert_rows.

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?

No guidance is provided on when to use this tool versus alternatives such as delete_columns or clear cells. There is no mention of prerequisites, edge cases, or when not to use it.

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