Get Range Formulas

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

Annotations already declare readOnlyHint=true, so the description adds value by explaining A1-style formula formatting, fallback to literal values for non-formula cells, and the JSON 2D array return shape. These details go beyond the read-only annotation without contradicting it.

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?

Front-loaded with the core purpose, then concise, well-structured Args and Returns sections. No redundant sentences; every line adds necessary context.

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 read-only tool with three optional parameters and no output schema, the description fully covers param meanings, default behaviors, and return format. Nothing essential for calling it correctly is missing.

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%, but the description compensates fully with an Args section explaining each parameter, including defaults (None = active workbook/sheet) and format examples (range_address 'A1' or 'A1:C10'). This is exactly the meaning an agent needs beyond bare parameter names.

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 begins with 'Read formulas from a cell or range', which states a specific verb and resource. The additional note that non-formula cells return literal values further clarifies its scope, distinguishing it from value-reading siblings like get_range_values.

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?

Usage is implied rather than explicit: reading formulas vs. values. No direct mention of when to use this tool over alternatives like get_range_values, nor any exclusions or prerequisites. The intent is clear but the guidance relies on inference.

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