sheets_read_range

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds value by specifying the return contract (JSON with range and values as a 2D array) and the caveat that empty trailing cells are omitted by Google's API. This is useful behavioral context beyond the annotations.

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 two short paragraphs with no filler. The primary verb/resource statement is front-loaded and the return shape is presented in a compact structured block.

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 read operation, the description, annotations, and schema cover the core workflow and return value. It is slightly incomplete only in lacking explicit alternative routing or error/format caveats beyond empty trailing cells, but nothing critical is missing.

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 description does not explain spreadsheet_id or A1 notation parameters, but the input schema's $defs provide descriptions for both, including the example format and source of the spreadsheet ID. This meets the baseline for schema-supported parameter semantics.

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 and resource ('Read cell values from a range in a Google Sheet') that clearly identifies the operation. This distinguishes it from sibling write/append/clear tools without needing to open the schema.

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 read-only wording implies the tool is for retrieving data, but it does not explicitly state when to prefer it over alternatives such as sheets_write_range, sheets_list_tabs, or drive_read_file_content. There is no when-not-to-use or exclusion guidance.

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