sheets_batch_get_values

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safe, idempotent behavior is covered. The description adds no further behavioral context, such as return format or rate limits, but it is consistent with the annotations and does not contradict them.

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, concise sentence with no redundant or filler words. It conveys the tool's core purpose immediately and saves the agent time.

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 straightforward read tool, the description is mostly sufficient, especially with detailed schema and annotations. However, since there is no output schema, it would be helpful to mention that the response returns a map of ranges to values, and that it is more efficient than multiple single-range calls. This minor gap prevents a perfect score.

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 provides 100% description coverage for all 4 parameters, including clear definitions and examples for ranges, spreadsheetId, majorDimension, and valueRenderOption. The description itself adds no parameter-specific meaning, so the baseline of 3 applies.

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 uses a specific verb 'Get' with resource 'values' and scope 'multiple ranges' in a Google Sheets spreadsheet. This clearly distinguishes it from sibling tools like sheets_get_values (single range) and write operations such as sheets_batch_update_values.

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 phrase 'multiple ranges' implies when to use this tool (when needing more than one range), but it does not explicitly state when not to use it or recommend alternatives such as sheets_get_values for single ranges. No exclusions or contrasting guidance are provided.

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