sheets_batch_update

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

No annotations provided, so description carries full burden. It mentions allowed request types but discloses no behavioral traits like destructiveness (e.g., deleting sheets), authorization needs, rate limits, or error behavior. A mutation tool should explicitly state side effects.

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?

Single sentence that is front-loaded, clear, and efficient. No filler words; every part conveys necessary 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?

With 2 parameters, no output schema, and critical side effects (e.g., deleting sheets), the description is too brief. It omits return value, prerequisites (spreadsheet must exist), atomicity, and potential impacts. For a complex batch tool, this is incomplete.

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 coverage is 100%, so baseline is 3. Description adds examples of request types, which mildly enriches the parameter description, but does not provide new structural or syntax details beyond what the schema already states.

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?

Clearly states the tool applies batch update requests to a Google Spreadsheet, and lists examples like formatting, add/delete sheets, merge cells, charts, conditional formatting. This distinguishes it from sibling sheets_batch_update_values (cell values) and other related tools.

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?

Implicitly suggests use for structural or formatting changes, but does not explicitly guide when to prefer this over alternatives like sheets_batch_update_values or when not to use it. No exclusions or when-not instructions.

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