Format Sheet Range

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

The description adds some behavior details beyond annotations, such as hex color format and Sheets number format types, and the default sheet selection. However, it does not disclose whether formatting merges with existing formatting or replaces it, nor any side effects or error behavior. The annotations already indicate non-readonly and non-destructive, and the description does not contradict them.

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 three concise sentences, front-loaded with the primary purpose, then elaborating with relevant parameter constraints. No redundant content, filler, or unnecessary details. Every sentence earns its place.

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?

For a tool with 13 parameters and annotations, the description covers the main purpose, key value format constraints, and default behavior. It does not need to explain return values due to the presence of an output schema. A minor gap is not stating the effect on existing formatting, but overall it provides adequate context for selection and usage.

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?

With 100% schema coverage, the schema already documents each parameter. The description enriches understanding by clarifying acceptable color formats (#RRGGBB), providing examples of number format types, and explaining the default sheet behavior for ranges without a sheet name. This adds value beyond the schema's brief descriptions.

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 identifies the tool's function with a specific verb ('Applies formatting') and enumerates the types of formatting (colors, number formats, wrapping, alignment, styling), distinguishing it from sibling tools like modify_sheet_values or read_sheet_values. It also adds a useful default behavior note, making the tool's scope unambiguous.

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 ranges but does not explicitly state when to use it over alternatives, mention exclusions, or reference sibling tools. The only contextual note is the default first-sheet behavior, which is more of a parameter detail than usage guidance. It provides some operational context but lacks explicit when/when-not guidance.

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