conditional_format

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

There are no annotations, so the description carries the full burden. It does disclose one meaningful behavioral trait: 'Removing rules is destructive to formatting state.' However, it gives only a vague return-type note and does not explain side effects of applying rules, rule precedence, or Excel-specific limitations—even though it acknowledges these as gaps.

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 structured with Args, Returns, and Notes sections, making it easy to scan. The parameter list is long but necessary given the 20-parameter schema. The final note 'Consider documenting rule precedence and Excel-specific limitations' is more of a meta-suggestion than tool guidance, which slightly detracts.

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?

This is a high-complexity, multi-action tool with 20 parameters and no annotations. The description provides a high-level overview but does not explain which parameters are required for each action, how actions interact, or behavioral edge cases. The output schema covers return structures, but the usage context for such a flexible tool remains incomplete.

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 adds value by grouping parameters into categories like 'Visual rule parameters' and 'Rule parameters for highlight/formula rules,' and it explains the action enum values. However, many parameters (e.g., rank, percent, equal_average) are only labeled as 'Additional rule params' without detailed semantics.

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 begins with a specific verb phrase: 'Apply, list, or remove conditional formatting rules on a sheet.' This clearly states the tool's core function and differentiates it from sibling formatting tools like format_cells or clear_cell_format by focusing on conditional formatting rules. The multi-action scope is explicit.

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 through the action enum list, but it does not explicitly state when to use this tool versus alternatives such as format_cells or data_validation. It also lacks exclusion criteria or context for choosing between the different actions beyond their names.

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