sheets_values_get

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

No annotations are provided, so the description carries the full burden. It only states the basic operation but omits details about authentication, rate limits, error handling (e.g., invalid range), or response shape. The description is minimal and does not disclose behavioral traits beyond the obvious read operation.

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 phrase 'Read values from a spreadsheet range.' It is front-loaded and to the point. However, it could be slightly more structured, but there is no wasted text.

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?

There is no output schema, so the description should explain what the tool returns. It does not mention the return value (e.g., an array of arrays of values). For a read tool, this is a significant gap. The description is incomplete for an agent to understand fully what it will receive.

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?

Schema description coverage is 100%, so each parameter already has a description in the input schema (e.g., spreadsheetId, range, majorDimension, valueRenderOption). The tool description adds no extra meaning beyond what is already in the schema. Baseline 3 is appropriate.

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 values from a spreadsheet range,' specifying the verb 'Read' and the resource 'values from a spreadsheet range.' It distinguishes from siblings like sheets_values_append and sheets_values_update which write, and sheets_get which retrieves sheet metadata.

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 does not provide explicit when-to-use or alternatives. However, given the tool's name and the sibling list, it is obvious that this is for reading values; other sibling tools handle writing or metadata. Still, no explicit guidance on when not to use or preferred context.

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