append_table_rows

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: mutation, auto-extending range, automatic type conversion (bool, number, formula), and OAuth scope requirement. It lacks explicit error conditions or idempotency, but covers essential traits well.

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 concise with two short paragraphs. It front-loads the purpose and uses clear, non-redundant language. Every sentence adds value with no 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?

Given the tool complexity (mutation with typing) and presence of an output schema, the description covers purpose, side effects, typing, alternatives, and auth scope. It omits error handling and return value details, but is largely complete for agent usage.

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?

Input schema coverage is 100%, so baseline is 3. The description does not add significant meaning beyond the schema. It mentions auto-extending range related to values, but no additional parameter-level details.

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 'Append rows to a structured Sheets table, auto-extending its range.' It uses a specific verb+resource and explicitly distinguishes from the sibling tool modify_sheet_values for plain range writes.

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 provides explicit guidance on when to use this tool (for structured table appends) and when not to (use modify_sheet_values for plain range writes). It also mentions prerequisites like table_id from list_sheet_tables.

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