read_range

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

With no annotations, the description carries the full behavioral burden. It clearly states the operation is read-only, explains how the values parameter distinguishes cached/formula/both modes, and discloses the subtle 'absent' labeling for formula cells without cached values instead of presenting them as blank.

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 definition is dense but compact: each clause adds a distinct fact, and the important scope and read-only property appear early. The values modes are clearly separated with quoted literals rather than buried in a long paragraph.

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 4-parameter read tool with an output schema, the description covers operation, location variants, value semantics, sheet defaults, and the large-range alternative. It is incomplete only because path is left undefined and the exact JSON structure of the location object is not shown beyond naming its forms.

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 0%, so the description must compensate. It richly defines location (with nine accepted forms) and the values options, and explains sheet fallback, but it never explains the required path parameter, leaving a meaningful gap for a required input.

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 opens with a specific verb-resource pair, 'Read a cell or range,' and then enumerates the accepted location object forms. It also distinguishes itself from siblings by stating it is read-only and pointing large-range reads to query_range, so it is not confused with write or query tools.

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?

It explicitly says to page large ranges with query_range, giving one concrete alternative. It also implies read-only use is the intended context, but it does not enumerate when not to use read_range versus other read-oriented siblings such as get_cells.

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