set_cell_style

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

With no annotations, the description clearly discloses partial updates, non-rollback behavior, and a dry_run parameter. It covers formatting details and border structure but omits potential limits like cell count or rate limits.

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 well-structured with a main statement, a warning, and a parameter list. It is efficient but could omit the 'Args' section formatting slightly to reduce redundancy.

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 11 parameters, 3 required, no annotations, and no output schema, the description covers parameter meanings adequately. It explains all optional parameters, but lacks specification of return values or success indicators.

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?

Despite 0% schema description coverage, the description provides detailed parameter explanations: formats for colors ('#RRGGBB'), border structure, range convention ('bare A1 without sheet prefix'), and dry_run purpose. This fully compensates for the schema gap.

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?

Description clearly states 'Style cells' with specific behavior: 'Only the parameters you pass are changed; the rest is preserved.' This differentiates it from sibling tools that update values or set number formats.

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 warns about no rollback capability and suggests using Sheets version history, but does not explicitly compare with alternative styling tools or provide when-to-use/not-to-use guidance relative to siblings like set_number_format.

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