format_range

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

Annotations indicate `destructiveHint: true`, so the agent knows the operation is potentially destructive, but the description adds little beyond that. It does not mention whether existing formatting is overwritten, whether the file is modified in place, or how `dry_run` or `include_changes` affect behavior. This is a significant transparency gap for a mutation tool.

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 two sentences, front-loaded with the main action. No redundant words. However, the second sentence, while useful, is narrowly focused on color formats and could be expanded to cover other key parameters without becoming verbose.

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?

This is a complex tool with 20 parameters and no output schema, yet the description provides only a high-level purpose and color format syntax. It lacks critical context such as how to specify the range, what `dry_run` does, what `protection` accepts, and what the result of the operation is. The tool is considerably under-described for its 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?

Schema description coverage is 0%, so the description must compensate, but it only explains the accepted color formats (RRGGBB, #RRGGBB, etc.) for color-related parameters. The other 17 parameters (e.g., `dry_run`, `protection`, `conditional_format`, `border_style`) are left entirely unexplained, so the description adds minimal value for most parameters.

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 applies formatting to a range of cells, which is a specific verb+resource. However, it does not distinguish this tool from the sibling `format_ranges` (plural), so the purpose is clear but not fully differentiated.

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 no guidance on when to use this tool versus alternatives such as `format_ranges`, `read_range_formatting`, or `copy_range`. There is no mention of exclusions, prerequisites, or ideal use cases, leaving the agent without contextual selection criteria.

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