batch_write

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

No annotations provided, so description must carry full burden. It discloses the API method ('batchUpdate') and data shape, but lacks details on side effects (e.g., overwriting existing values), permissions, rate limits, or error handling.

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?

Two concise sentences with a clear, front-loaded purpose. The example is embedded efficiently, providing essential context without extraneous text.

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?

For a batch write tool with 3 parameters and no output schema, the description covers the critical data format and operation scope. It could mention prerequisites (e.g., sheet existence) or return behavior, but overall is sufficient.

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 compensates by detailing the 'data' parameter with a concrete example of the ValueRange shape. However, it adds no extra meaning for 'spreadsheet_id' or 'value_input_option' beyond schema titles/defaults.

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?

Description clearly states the verb 'Write values to multiple ranges' and the resource 'values batchUpdate call'. It differentiates from single-range writes like 'write_range' by emphasizing 'multiple ranges'.

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?

Description implies use for batch updates but does not explicitly state when to prefer this over siblings (e.g., 'write_range' for single range). No exclusions or alternatives are mentioned, leaving the agent to infer context.

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