read_sheet

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

With no annotations, the description carries the full burden. It discloses the return format (2D array), absolute addressing from A1, the default behavior of reading the full used area, and the max_rows cap. It does not mention error cases or auth requirements, but for a read operation this is reasonably transparent.

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, front-loaded with the main purpose, and each parameter explanation adds value. No redundant or filler content.

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 the output schema exists, the description need not explain return values. It covers core behavior, common parameter combinations, and the max_rows guard against large responses. Minor gaps remain around error handling and behavior when path is ambiguous, but overall it is complete for this tool's complexity.

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?

All four parameters receive meaningful explanation beyond the schema: path is described as a file path or preloaded file with an omission rule, cell_range is given with an A1-style example and default behavior, and max_rows is explained as a response-size bound. This fully compensates for the 0% schema description coverage.

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 cell values from a sheet as a 2D array with absolute A1 addressing. It distinguishes this from sibling tools like get_cell by specifying the bulk/2D array behavior.

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 description gives useful guidance for when to omit path, cell_range, and max_rows, but it does not explicitly explain when to use this tool over alternatives such as get_cell, aggregate_sheet, or search_workbook. No exclusionary or alternative-tool guidance is provided.

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