spreadsheet_update

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

Discloses that it is a write operation, waits for async completion, and has formatting constraints. Without annotations, the description carries the full burden and adequately conveys key behaviors.

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?

Three concise sentences with no redundancy. Each sentence adds value: purpose and options, formatting tip, and async behavior.

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 presence of an output schema, the description does not need to detail return values. It covers the essential behavioral and usage aspects for a write operation.

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 meaningful context to operations_json by enumerating valid values and noting index behavior (0-based, inclusive). With 0% schema coverage, this compensates well, though spreadsheet_id and sheet_id lack added detail.

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 explicitly states 'WRITE. Write to a sheet,' clearly identifying the verb and resource. It also lists the allowed operations (editRange, editCells, applyFormats, resizeColumns), distinguishing it from sibling tools like spreadsheet_list_sheets.

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 usage tips such as sending numbers as JSON numbers and referencing a KB article, but does not explicitly state when to use this tool versus alternatives or when not to use it.

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