Modify Sheet Values

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description aligns by mentioning 'modify' and 'clear', but adds no new behavioral details beyond what annotations provide (e.g., no mention of permissions, formula impact, or side effects).

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 a single concise sentence (17 words) that front-loads the main action. No redundant or unnecessary text.

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?

The description covers the basic purpose but lacks important context for a multi-mode tool, such as how values and clear_values interact (e.g., omit values when clearing). Given the output schema exists, return values are likely covered elsewhere, but the description could be more helpful for 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?

Schema description coverage is 100%, so baseline is 3. The description does not add extra meaning about parameters; the schema already describes each parameter adequately.

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 tool modifies values in a Google Sheet range, listing specific operations: write, update, or clear. It uses a specific verb and resource, and implicitly distinguishes from siblings like read_sheet_values (read-only) and append_table_rows (append mode).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., append_table_rows for appending). The agent must infer from sibling names, which is insufficient for a tool with many siblings and multiple modes (write vs clear).

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