write_range

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

No annotations are provided, so the description must cover behavioral traits. It states that values are stored as formulas if they start with '=' and that null clears a cell, but it does not disclose whether the write overwrites existing data, what happens if the range extends beyond the sheet, or any error conditions. More context is needed.

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 concise (3 sentences) and front-loaded with the main action. It efficiently explains key parameter behavior. Could be slightly improved by mentioning return value or side effects.

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 no annotations or output schema, the description is reasonably complete for a basic write operation but lacks details on return value, error handling, and behavior when overwriting existing data or exceeding sheet bounds.

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?

With 0% schema coverage, the description adds significant meaning to the 'values' parameter by explaining it is a list of rows with examples and special handling of formulas and nulls. However, 'session_id' and 'start_cell' are not elaborated beyond their names, which are self-explanatory.

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 a 2D array of values starting at start_cell', specifying the verb 'Write', the resource (range of cells), and the data format (2D array). This distinguishes it from sibling tools like write_cell (single cell) or append_rows (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?

The description implies usage for writing a rectangular block of data, but it does not explicitly state when to use this tool versus alternatives like write_cell, append_rows, or replace_in_range. No alternatives or exclusions are mentioned.

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