format_range

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

Annotations include destructiveHint: true, but the description adds no behavioral context beyond listing parameters. It does not disclose that formatting overrides existing styles, that it may be irreversible, or any auth/rate-limit requirements. The description adds minimal value over the annotation.

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 a focused bullet list, each line covering one parameter with a brief explanation. No redundant sentences, though some entries are minimal. Well-structured for readability.

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 13 parameters, no output schema, and no return value documentation, the description is incomplete. It does not explain what happens after formatting (e.g., success/error), behavior with partial parameter sets, or how defaults are applied. The high complexity warrants more coverage.

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%, so the description must compensate. It provides examples (e.g., hex colors, number format like '#,##0.00') and explains alignment values. However, many parameters like 'bold' or 'italic' are just restated from the schema with 'Set bold/italic' offering no additional semantic depth. Overall, it adds some but not full 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 verb 'Apply formatting' and the resource 'cell range', with a comprehensive list of formatting options. It distinguishes from sibling tools like 'write_data' (value writing) and 'read_data' (reading values) by focusing on formatting only.

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 for formatting a range but provides no explicit guidelines on when to use this tool versus alternatives like 'get_cell_styles' (reading styles) or 'find_replace'. No when-not-to-use 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.