sheets_write_range

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

No annotations are provided, so the description carries full burden. While it indicates mutation ('write'), it doesn't disclose whether the operation overwrites data, affects formatting, or has side effects like sheet creation. Behavior such as error handling or size limits is omitted.

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 two sentences: the first states the purpose, and the second provides a concrete example. It is concise, front-loaded, and contains no extraneous information.

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 has three parameters, no output schema, and no annotations, the description is adequate but incomplete. It covers the basic operation and value format but omits important context like range must exist, what happens on conflict, or success indication.

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 already describes all three parameters with 100% coverage. The description adds value by explaining the expected structure of 'values' as a 2D array with an example, which clarifies beyond the schema's generic description. It does not elaborate on the 'spreadsheet' parameter but the example aids understanding.

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 'Write values to a Google Sheet range,' specifying the verb and resource. It distinguishes from siblings like sheets_read_range and sheets_append_row by indicating a write operation, and provides an example format for the values.

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 does not provide guidance on when to use this tool versus alternatives (e.g., when to use write vs append). It lacks prerequisites, such as requiring the sheet to exist, and does not mention when the optional spreadsheet ID is necessary.

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