Batch Get Spreadsheet Values

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, which cover safety. The description adds valuable behavioral context by specifying the output format options (markdown vs JSON) and including an example JSON response structure, which goes beyond the annotation hints.

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 well-structured with Args, Returns, and Examples sections, and it is front-loaded with the main purpose. However, the Args section largely duplicates the schema, making it somewhat repetitive, though not wasteful.

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 no output schema, the description compensates by providing a full example of the JSON response format and a usage example. It covers all parameters, defaults, and return behaviors, making it sufficiently complete for an agent to correctly select and invoke the 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?

The input schema covers 100% of parameter descriptions, so the baseline is 3. The description repeats the parameter details and adds a usage example for ranges, but it does not introduce new semantic information beyond the schema's own descriptions and 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?

The description clearly states the tool reads cell values from multiple ranges in a single request, using a specific verb ('Read') and resource ('cell values from multiple ranges in a Google Spreadsheet'). This distinguishes it from sibling tools like sheets_get_values (single range) and sheets_batch_update (write operation).

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 implies the primary use case ('multiple ranges in a single request') but does not explicitly mention when to prefer this tool over alternatives like sheets_get_values or sheets_batch_update. There is no explicit exclusion or comparison, leaving the agent to infer the batching advantage.

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