Move Sheet Rows

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

The description reveals important behavioral traits beyond annotations: the batchUpdate process (copyPaste followed by deleteDimension), potential partial failure leading to duplicate rows, and preservation of formulas/data types/formatting. This adds significant value as the annotations only indicate destructiveness.

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 three sentences with no filler. First sentence states purpose, second explains batchUpdate behavior and risk, third clarifies row numbering. Every sentence contributes essential information without redundancy.

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 parameters, output schema present), the description covers all necessary aspects: purpose, mechanism, failure mode, data preservation, and numbering convention. It does not need to explain return values as an output schema exists. This is comprehensive for the tool's nature.

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?

While the schema covers 100% of parameters, the description adds useful context: row numbers are 1-based (matching UI) and row range is inclusive. This goes beyond the schema descriptions which already mention 1-based. The extra note about inclusive range and UI alignment provides marginal added value.

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 tool moves rows between sheets within the same spreadsheet, which is a specific verb and resource. It distinguishes itself from sibling tools like append_table_rows or modify_sheet_values by focusing on move operations with batch update behavior.

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 does not explicitly state when to use vs alternatives, but it contrasts with a values.get/append round-trip, implying this tool is better for preserving formulas and formatting. However, no direct exclusion criteria or alternative recommendations are given.

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