sheets_raw_batch_update

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

Despite no annotations, the description discloses key behaviors: atomicity (all-or-nothing) and efficiency (single round-trip). It also signals 'raw' requests, implying these are passed to the API as-is without validation. However, it doesn't mention error handling, response structure, or authorization requirements, leaving gaps for a raw mutation tool.

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 immediately states what the tool does, why it's useful, and how it differs from alternatives. No wasted words; every element adds value.

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 (raw API requests, arbitrary nested objects), the description is too thin. It doesn't mention that requests must conform to the Sheets API batchUpdate format, what the response contains, or failure modes—even though an output schema exists, the agent lacks guidance on constructing valid requests. The atomicity hint helps but is insufficient for a raw API tool.

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 0%, so the description must compensate. It explains that the 'requests' parameter is a list of raw Sheets API batchUpdate requests, providing essential meaning beyond the schema's generic 'array of objects'. It doesn't elaborate on the structure of each request or explicitly describe 'spreadsheet_id', though the name and context imply its purpose.

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 applies raw Sheets API batchUpdate requests in one round-trip. It distinguishes itself from higher-level sheet tools by emphasizing 'raw' requests and combining many edits atomically, which differentiates it from sibling tools like sheets_batch_update.

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 clear usage context: use when you need to combine many structural/formatting edits into a single atomic round-trip instead of multiple tool calls. It doesn't explicitly mention alternatives or when-not-to-use, but the 'instead of many tool calls' phrasing implies the comparison.

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