append_rows

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

Description discloses non-destructive nature, and explains the behavior of 'value_input' (RAW vs USER_ENTERED) and 'dry_run' (predicted location without appending). Annotations already indicate non-destructive, so description adds value beyond annotations.

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?

Three sentences, no wasted words. Purpose is front-loaded, parameter explanations are concise. Every sentence adds value.

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?

Covers purpose, non-destructive behavior, and key parameters. However, lacks details about return value (no output schema), error handling, or constraints like row array structure. Adequate but not complete for a tool with 5 parameters.

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 description coverage is 0%, so description compensates partially by explaining 'value_input' and 'dry_run' parameters. However, required parameters ('tab', 'item', 'rows') lack additional meaning beyond the schema. The added details for two optional parameters raise it above baseline 1, but not enough to be a 4.

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 clearly states the tool appends rows after the last row of a spreadsheet tab. It specifies the resource (spreadsheet tab) and action (append rows), and distinguishes itself from siblings like 'write_sheet' by being non-destructive.

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?

Description mentions non-destructive but provides no guidance on when to use this tool versus alternatives like 'write_sheet' or 'clear_range'. No explicit when-to-use or when-not-to-use context is given.

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