append_rows

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

With no annotations, the description carries full burden and adequately discloses key behaviors: it never overwrites, explains dry_run returns an execution plan, raw stores inputs literally, and force allows bypassing cell limits. However, it does not describe the return format or pagination behavior.

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 highly concise: one sentence for the main purpose followed by efficient bullet points for each parameter. No redundant or extraneous information; 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?

Given the tool's moderate complexity (6 params, 3 required, nested rows, no output schema), the description covers core behavior, parameter details, and edge cases (force limit, dry_run). It lacks explanation of the dry_run execution plan format and return value structure, but overall it is sufficient.

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?

The description provides detailed explanations for all 6 parameters, compensating for 0% schema description coverage. For example, it clarifies spreadsheet_id_or_url accepts 'Full URL or bare ID', sheet is 'name OR gid', rows is '2D list', and explains the effects of raw, dry_run, and force.

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 action ('Append rows after the last data row of a sheet') and explicitly distinguishes it from overwriting, which differentiates it from sibling tools like update_range. The verb 'append' and resource 'rows' are specific and unambiguous.

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?

While the description implies use for adding data without altering existing rows, it does not explicitly state when to use this tool versus alternatives like insert_rows or update_range. No direct 'when-to-use' or 'when-not-to-use' guidance is provided.

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