Get Spreadsheet Values

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

Annotations already establish this as a safe, idempotent read operation. The description adds transparency about return formats (markdown/json) and the structure of JSON responses, which is beyond the annotations. It also documents default parameter values, but doesn't address edge cases like invalid ranges.

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 clear sections for arguments, returns, and examples. It is concise and front-loaded with the core purpose, with no redundant filler.

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?

Given the tool's simplicity and rich annotations, the description is mostly complete. It covers all parameters, provides examples, and describes the JSON return structure. The markdown output format is only described as 'human-readable' without specifics, and there's no mention of error behavior, leaving minor gaps.

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 already provides descriptions for all four parameters, so the baseline is 3. The description enhances this by providing explicit examples of range patterns (e.g., 'Sheet1!A:A') and the default values for optional parameters. It also clarifies the output structure for the 'json' response_format, adding practical value.

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 'Read cell values from a specific range in a Google Spreadsheet' with a specific verb and resource, and differentiates from sibling tools like sheets_batch_get_values by focusing on a single specific range. The inclusion of examples reinforces the exact 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 provides examples but does not explicitly compare against alternatives such as sheets_batch_get_values for multiple ranges or sheets_get_spreadsheet for metadata. Usage guidance is implied by the operation's simplicity, but there are no explicit when-to-use or when-not-to-use statements.

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