append_rows

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

No annotations are provided, so description carries burden. It states the mutation (append) and describes return format (JSON with updated range and appended cells), but does not disclose permissions, side effects on existing data, or behavior with empty ranges.

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?

Two sentences plus compact Args/Returns list; front-loaded with the core purpose. No filler or redundant wording.

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 three-param append tool with an output schema, it covers purpose, each parameter, and return format. Lacks explicit usage guidance versus sibling tools and edge-case behavior, but overall adequate.

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 has zero descriptions for all three parameters, and the description compensates fully by explaining each parameter's meaning: spreadsheet ID, A1 range notation, and JSON 2D array of rows. Includes example for range_notation.

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 specific verb 'Append' and resource 'rows to the end of data in a sheet', clearly distinguishing from insert_rows and write_cells by specifying end-of-sheet 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?

Implies appending to end-of-sheet but does not explicitly state when to choose this over insert_rows or write_cells. It provides clear context (appending) but no exclusions or alternative comparisons.

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