get_formulas

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

Annotations include readOnlyHint=true, and the description goes beyond by explaining that only formula cells are returned and that values_too includes calculated values. This adds context about the tool's behavior without contradicting annotations.

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 a clear header and bullet-pointed arguments. Every sentence is informative, no redundancy, and the main purpose is front-loaded.

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 retrieval tool with 4 parameters and no output schema, the description covers purpose, parameters, and defaults. It could mention return format or behavior when no formulas exist, but overall is sufficient.

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 fully documents each parameter: cell_range ('Range like A1:U99'), workbook (name/path, defaults to active), sheet (defaults to active), values_too (include values). This adds meaningful details beyond the schema's type-only definitions.

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 'Get all formulas in a range. Returns only cells that contain formulas.' This uses a specific verb and resource, and distinguishes itself from sibling tools like read_data (which returns all values) and find_replace (which modifies).

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 implies usage through 'Returns only cells that contain formulas,' suggesting use when formulas are needed versus values. However, no explicit when/when-not or alternatives are mentioned, missing opportunities to differentiate from read_data.

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