sheets_format_cells

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the categories of formatting, not behavior such as whether existing formatting is overwritten or if specific permissions are needed, but it does not contradict 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?

A single, front-loaded sentence efficiently conveys the tool's purpose and key formatting areas without waste. It is appropriately sized for the annotation-rich 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?

Given the complex nested format schema and annotations, the description is minimally viable but lacks important context such as when to choose this over batch formatting or what happens to existing formats. The schema and annotations compensate partially, but the description alone is not fully complete for a tool of this 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. It lists high-level categories (colors, fonts, alignment, number formats) that map to the format object's properties, aiding interpretation. However, it does not explain individual parameters like padding or wrapStrategy; the detailed schema carries most semantic weight, resulting in adequate but not strong compensation.

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 formats cells in a Google Sheet and lists the main formatting categories (colors, fonts, alignment, number formats). This is a specific verb+resource combination that distinguishes it from broader sheet operations, though it does not explicitly differentiate from the sibling sheets_batch_format_cells.

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?

No guidance is provided on when to use this tool versus alternatives like sheets_batch_format_cells, nor any prerequisites such as access requirements or range formatting behavior. The description gives no contextual clues for selection beyond the basic purpose.

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