sheets_append_values

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

With no annotations, the description must disclose behavior. It reveals the critical default overwrite behavior and the option to insert rows, which is good. However, it lacks information about permissions, error conditions, response format (no output schema), and rate limits, leaving some behavioral gaps.

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 extremely concise with two sentences. The first sentence states the core purpose, and the second adds a crucial behavioral note. No wasted words; every sentence earns its place. It is front-loaded and easy to parse.

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 moderate complexity (5 parameters, 3 required) and no output schema, the description provides adequate context for basic use. It explains key behavior but omits details like return values, error scenarios, and prerequisites. It is sufficient but not comprehensive.

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 input schema has 100% coverage, so the description does not need to repeat parameter definitions. It adds value by explaining the effect of the insertDataOption parameter and its default, but does not elaborate on other parameters like valueInputOption or range beyond what the schema provides.

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 values to the end of a table in a Google Sheets spreadsheet') with a specific verb and resource. It distinguishes the tool from siblings like sheets_update_values by focusing on appending, but it does not explicitly call out when to use this tool over others.

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 important usage guidance by highlighting the default overwrite behavior and how to change it to insert rows via insertDataOption. However, it does not give guidance on when to choose this tool over alternatives (e.g., sheets_update_values) or mention prerequisites.

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