Append to spreadsheet

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

No annotations are provided, so the description carries the full behavioral burden. It states that rows are appended below existing data, which implies a non-destructive addition, but it does not disclose response behavior, whether existing data is preserved explicitly, how valueInputOption affects results, or any side effects.

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 a single concise sentence that is front-loaded with the core action and target resource. It contains no filler or redundant phrasing.

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 simple append operation, the description conveys the essential behavior, and the schema covers parameter details. However, with no annotations and no output schema, the description leaves out return-value expectations and selection guidance relative to the many sheet-related siblings.

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?

The input schema already covers all five parameters with 100% description coverage, including the A1 range format, the values array of rows, and the valueInputOption enum. The description adds no additional parameter meaning, which is acceptable given the schema completeness.

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 uses a specific verb and resource: 'Append rows below the existing data in a sheet.' It clearly communicates the operation and its positional behavior. It distinguishes itself from siblings like google_sheets_write by emphasizing appending below existing data, though it does not explicitly name alternatives.

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 phrase 'below the existing data' implies the tool is appropriate when adding rows without overwriting current content. However, there is no explicit guidance about when to choose this over google_sheets_write or google_sheets_batch_update, and no exclusions or conditions are stated.

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