read_cells

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions that 'Empty cells may be omitted' and specifies the return format as a JSON 2D array, which are useful behavioral details. It does not cover error conditions, but for a read operation this is reasonable.

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 a one-sentence summary, then examples, args, and returns. Each section adds value without redundancy, and the information is front-loaded in the first line.

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 two-parameter read tool, the description covers operation, parameters, usage examples, and return format. The presence of an output schema reduces the need to detail return structure further, and the description is sufficient for an agent to invoke the tool correctly.

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 schema provides only parameter names and types, with zero coverage in the schema descriptions. The description compensates fully by explaining spreadsheet_id as 'The ID from the spreadsheet URL' and range_notation with A1 notation format and examples.

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 spreadsheet range' with a specific verb and resource, and the examples clarify the exact operation. However, it does not explicitly distinguish this tool from the sibling batch_read, which might be the multi-range alternative.

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 examples show how to use the tool and what range notations are valid, but there is no explicit guidance on when to choose read_cells over alternatives like batch_read or get_last_row. The context is implied rather than stated.

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