sheets_batch_get

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

The description provides no information about side effects (though it is clearly a read operation), return format, error handling, pagination, or other behaviors. Without annotations, the description carries the full burden, and it only states the basic action.

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 one clear sentence with no unnecessary words. It immediately conveys the tool's function and scope.

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 simple batch read operation, the description provides the core context (multiple ranges, single request). However, it lacks details about the expected response structure, how ranges are formatted, or how valueRenderOption affects results—information that would help an agent use the tool effectively.

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 schema includes descriptions for spreadsheetId and ranges, but valueRenderOption lacks a description. Coverage is 67% (2 of 3 parameters), which is above the 50% threshold but below 80%. The existing descriptions are minimal but sufficient for those parameters.

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's purpose: to retrieve data from multiple ranges in a single request. It directly contrasts with the sibling tool sheets_get_data, which presumably handles a single range, making the batch nature explicit.

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?

While the description implies usage for fetching multiple ranges at once (as opposed to the single-range sheets_get_data), it does not explicitly state 'use this instead of sheets_get_data for multiple ranges'. The guidance is sufficient but not directly stated.

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