read_sheet

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

Discloses truncation at 10,000 cells and explains the return format when first_row_is_header is true. No annotations are provided, so the description takes on the transparency burden well, though it omits default return format and error conditions.

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 very concise with two sentences, front-loading the main purpose. Every sentence provides essential information without waste.

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?

Given no output schema, the description covers the return format for the header case and mentions truncation. It does not mention default output format (list of lists) or error handling, but for a simple read tool it is reasonably 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?

With 0% schema description coverage, the description explains the sheet parameter (omit for active sheet) and the first_row_is_header parameter (changes return format). The required session_id is not explained but is likely standard. Overall, it adds meaningful value.

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 a whole sheet's used range', which specifies the verb and resource. It distinguishes from sibling tools like read_range (which reads a specific range) and read_cell (single cell).

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?

Provides guidance on omitting the sheet parameter for the active sheet and notes the truncation limit. However, it does not explicitly compare to alternatives like get_used_range or read_calculated_range, leaving some usage ambiguity.

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