Get Range Values

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

Annotations already include readOnlyHint=true, and the description confirms a read operation. It goes beyond annotations by disclosing the return format (JSON with a 2D array even for a single cell) and default parameter behavior (None = active workbook/sheet), which is valuable context.

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 and well-structured with Args and Returns sections. The main purpose statement is front-loaded, and every sentence provides necessary information. No fluff.

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?

There is no output schema, so the description properly explains the return format. It covers all parameters, defaults, and return behavior. The tool's simplicity and read-only nature means nothing critical is missing for an agent to invoke it 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?

Schema description coverage is 0%, so the description must compensate. It explains each parameter in the Args section, including example for range_address ('A1' or 'A1:C10'). This fully covers the 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 states 'Read values from a cell or range in an open workbook,' which is a specific verb and resource. It clearly distinguishes from sibling get_range_formulas by emphasizing 'values' rather than formulas. The scope is well-defined.

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 provides clear context: it reads values from a range, and the default behavior for workbook/sheet is explained. However, it does not explicitly mention when not to use it (e.g., when formulas are needed) or name an alternative tool, so it lacks explicit exclusions.

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