Batch update spreadsheet

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

No annotations are provided, so the description carries the full burden. It mentions 'raw' and examples of operations, but does not disclose potential side effects (e.g., data loss from deleting sheets), required permissions, whether changes are reversible, or what the return value looks like. This is a significant gap for a tool that can perform destructive batch operations.

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, front-loaded sentence that states the verb ('Send'), resource ('raw Sheets batchUpdate requests'), and examples, with zero wasted words. It is appropriately concise for a tool that references an external API.

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's complexity and absence of an output schema, the description is adequate but thin. It explains the core purpose and gives examples, but it does not mention that the tool passes requests directly to the API, that operations are applied in order, or any caveats about quota/rate limits or error propagation. It is minimally complete for an expert user.

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%, but the param descriptions are minimal ('Spreadsheet ID.', 'Sheets API batchUpdate requests.'). The tool description adds context by listing examples of request types (add/delete sheets, formatting), but it does not explain the structure of the requests array or how to construct the batchUpdate payload beyond what the schema already says. This is baseline for a schema with full coverage.

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's function: 'Send raw Sheets batchUpdate requests' with concrete examples like 'add/delete sheets, formatting.' This distinguishes it from sibling tools like google_sheets_write/append/read, which handle simpler, higher-level operations.

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?

Usage is implied via the word 'raw' and the examples of structural changes, suggesting it is for advanced operations not covered by other tools. However, it does not explicitly mention when to prefer this tool over alternatives like google_sheets_write or append, nor does it state any exclusions or prerequisites.

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