sheets_values_get

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

The readOnlyHint annotation already informs the agent that this is a safe read operation. The description adds no further behavioral context, such as data format, pagination, or error handling. With annotations covering safety, a score of 3 is appropriate—adequate but lacking extra detail.

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, front-loaded sentence of seven words, with no redundancy. While concise, it could include slightly more context without becoming verbose, but it earns a 4 for efficiency.

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 simple read operation and no output schema, the description provides the minimum necessary information. It does not explain the return format (e.g., 2D array), but the agent can infer from typical spreadsheet API behavior. Sibling tools are diverse, but the purpose is sufficiently clear.

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?

All four parameters are documented in the input schema (100% coverage). The description does not add extra meaning beyond the schema, so the baseline score of 3 applies. The schema already explains range format, majorDimension options, and valueRenderOption choices.

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 verb 'Read' and the resource 'values from a spreadsheet range', accurately conveying the tool's function. It distinguishes from sibling write tools (sheets_values_append, sheets_values_update) and possibly from sheets_get (sheet metadata), making selection unambiguous.

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?

No guidance is given on when to use this tool versus siblings. For example, it does not contrast with sheets_get (which reads sheet properties) or sheets_values_update (which modifies values). The agent must infer from the name and schema alone.

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