read_range

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

The description discloses the truncation limit (10,000 cells) and the inclusion of truncated and next_range in the response. With no annotations provided, the description carries the full burden, and it covers important behavioral aspects.

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 concise with two sentences, no redundant information. It front-loads the main purpose and adds essential details about truncation.

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 tool with two parameters and no output schema, the description covers the core behavior: reading a range, truncation, and continuation. It lacks guidance on range format but is otherwise complete.

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 input schema has no descriptions for params (0% coverage), but the description adds meaning by explaining the output is a 2D array. However, it does not specify the expected format of the range string (e.g., 'A1:C10'), leaving ambiguity.

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 tool reads a rectangular range and returns a 2D array of cell values. It distinguishes from siblings like read_cell (single cell) and read_sheet (whole sheet) by specifying the output format.

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 explicit guidance on when to use this tool versus alternatives. The purpose is clear from the name, but the description does not provide contextual cues for selection.

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