sheets_write_range

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

Annotations already include destructiveHint=true and readOnlyHint=false, and the description reinforces and explains the destructive behavior: the overwritten area is determined by the number of rows/columns in values starting at the top-left of range. It also discloses the return fields, going beyond annotations without contradicting them.

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 compact and well-organized: core behavior first, alternative tool second, return format last. Every sentence provides necessary information without filler.

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?

For a straightforward write operation, the description covers the operation, the overwrite semantics, the alternative tool, and the return value. Combined with the schema and annotations, an agent has enough context to invoke this tool correctly.

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 adds useful semantic meaning to values and range by explaining how they interact, but it does not mention spreadsheet_id at all. Given the reported 0% schema description coverage, the description only partially compensates for parameter-level guidance.

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 states a specific action ('Write values into a range') and the key consequence ('overwriting whatever is currently there'). It clearly distinguishes this tool from sibling sheets_append_values by emphasizing the difference between overwriting and appending.

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?

It explicitly tells the agent when to use sheets_append_values instead: when adding new rows without overwriting existing data. This is direct when-to-use versus when-not-to-use guidance, and it also clarifies how the values array determines the overwrite extent.

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