Append Table Rows

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

The description discloses that rows are added to the end of the table body and automatically extend the range, which complements the annotations (readOnlyHint false, destructiveHint false). It provides context beyond annotations by specifying the append location and range behavior. However, it does not discuss potential error conditions or side effects when values mismatch column structure.

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 long, each providing essential information: purpose, behavioral detail, and usage guidance. It is front-loaded and contains no superfluous words.

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 presence of an output schema and annotations, the description adequately covers how to use the tool (including prerequisite) and what to expect (append to end, extend range). It does not fully explain value format requirements or error handling, but these are partly addressed by the input schema. Overall, it is complete for the tool's simplicity.

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% with each parameter already described. The description repeats the table_id prerequisite found in the schema, adding no new parameter-specific information. Thus it meets the baseline but does not exceed it.

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 verb 'Appends', the resource 'rows to a structured table', and the context 'Google Sheet', distinguishing it from siblings like modify_sheet_values (modifies existing values) and create_table_with_data (creates new tables). The phrase 'automatically extending the table range' further clarifies the operation.

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 explicitly instructs to 'Use list_sheet_tables first to find the table ID', providing a clear prerequisite. It implies when to use this tool (append rows) but does not explicitly mention when not to use it or compare with alternatives like modify_sheet_values for inserting rows in other positions.

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