append_rows

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

No annotations were provided, so the description carries the full burden. It mentions that rows are appended below existing data and explains value_input_option behaviors, but it does not disclose non-destructive nature, permission requirements, rate limits, or return value expectations. Missing critical behavioral context for a data-modifying operation.

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 fairly concise with two short paragraphs. It front-loads the primary action and uses clear formatting for the value_input_option explanation. However, it could be tighter without losing clarity.

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 no output schema and many siblings, the description should be more comprehensive. It lacks details on edge cases (e.g., invalid range, overlapping data), return values, and behavioral nuances. The tool modifies data but misses necessary caveats.

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 needed to fully explain all parameters. It partially explains 'range' and 'value_input_option' but fails to describe the required 'values' parameter and the crucial 'spreadsheet_id'. The coverage is insufficient for an agent to confidently pass correct values.

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 appends rows after the last row in a given range. It distinguishes itself from siblings like append_columns_to_sheet and insert_rows, but does not explicitly differentiate from append_rows_to_sheet, and the phrase 'within/near' introduces slight ambiguity.

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 explains how the range selects the table and that new rows go below existing data, but it provides no guidance on when to use this tool versus alternatives like write_range or insert_rows. No explicit when-not or exclusions are given.

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