format_ranges

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

With destructiveHint=true, the description should clarify that existing formatting gets overwritten, but it only states 'Apply formatting' and adds color format variants. It does not disclose side effects like loss of prior formatting or whether the operation is reversible.

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?

Two short sentences, the first states the core purpose and the second gives color format details. No redundant content, but it is under-specified for a 5-parameter tool.

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?

With no output schema and sparse descriptions, the tool lacks essential context: the shape of range objects, behavior of optional flags, and expected return value. The one useful hint (color formats) is insufficient for correct invocation.

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 coverage is 0%, and the description only mentions color format syntax, leaving the structure of the 'ranges' objects and the purpose of dry_run/include_changes entirely unexplained. This does not compensate for the bare schema.

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 uses a specific verb ('Apply') and resource ('formatting to multiple ranges') and notes a single workbook pass, which distinguishes it from the singular format_range sibling. However, it doesn't explicitly name alternatives or detail what formatting entails beyond colors.

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 phrase 'in a single workbook pass' implies use for batched range formatting, but there is no explicit when-to-use or comparison to format_range or other formatting/reading tools. No exclusions or prerequisites are mentioned.

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