Move Sheet Rows

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

Discloses non-rollback partial failure and duplication risk, preservation of formulas/types/formatting, and 1-based row semantics, all beyond the annotations. The destructiveHint annotation is consistent with the described deleteDimension step, so no contradiction.

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?

Four dense, information-bearing sentences, front-loaded with the action; every sentence contributes essential behavioral context without fluff.

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?

Covers operation mechanics, failure behavior, preservation guarantees, and row numbering. Missing destination placement details (e.g., where moved rows land in destination sheet) is a minor gap, but annotations and output schema cover safety and return 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?

Schema coverage is 100%, so the schema handles per-parameter documentation; the description's 1-based/inclusive note partially repeats schema text. It adds no significant new parameter-level details beyond making the row-number convention explicit.

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?

Clearly identifies a specific operation (moving rows) with explicit scope (between sheets in the same spreadsheet). This distinguishes it from sibling tools like modify_sheet_values or append_table_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?

States that the operation uses batchUpdate rather than a values round-trip and explicitly contrasts with values.get/append behavior, giving context for when choosing this tool. It does not name alternative tools explicitly or list cases where a different operation should be used, but the purpose is specific enough to imply usage.

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