sheets_delete_rows

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

Annotations only include idempotentHint: true, with no destructiveHint. The description does not disclose permanent deletion, row shifts, or permission requirements. The verb 'Delete' implies destructiveness, but no additional behavioral context is provided.

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?

A single, front-loaded sentence that conveys the essential operation and input format with 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?

Adequate for a simple delete tool, but lacks usage differentiation and side-effect disclosure. Given many sibling delete-related tools, more context about selection criteria and consequences would improve completeness.

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 description coverage is 100%, with both parameters (range and spreadsheetId) already well-documented. The description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

Description uses a specific verb ('Delete') with a clear resource ('rows from a Google Sheet') and specifies the input format ('full-row A1 range'). This clearly distinguishes it from sibling tools like sheets_delete_columns or sheets_delete_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?

No guidance is provided on when to use this tool instead of alternatives such as sheets_delete_columns, sheets_delete_sheet, or sheets_clear_values. It does not mention prerequisites or context for choosing this tool.

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