get_cell_styles

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

The annotation indicates readOnlyHint=true, and the description adds behavioral context such as returning only non-default styles and listing filterable properties. However, it does not mention output format or error handling, and the description adds moderate value beyond 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?

The description is concise, starts with the main purpose, adds a key behavioral trait, and then lists parameters in a well-structured Args section with no unnecessary words.

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?

The description covers the tool's purpose, parameter explanations, and use cases, but lacks details about the output format and error handling, which is a gap given the absence of an output schema and the moderate complexity of four parameters.

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 0% schema description coverage, the description fully compensates by explaining each parameter: cell_range with example, workbook and sheet with defaults, and properties with a list of possible values, adding significant meaning beyond the schema.

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 'Get formatting/style info for cells in a range' and specifies that it returns only cells with non-default styles, distinguishing it from sibling tools like format_range (which modifies styles) and read_data (which reads values).

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 notes it is 'useful for identifying headers, subtotals, and data roles by visual formatting,' providing clear context for usage, but does not explicitly exclude alternatives or compare with siblings like format_range.

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