Clear Conditional Formatting Rules

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

Annotations already declare destructiveHint=true, and the description's 'Remove all' reinforces that destructive nature. It adds that the operation returns a JSON confirmation and that workbook/sheet can default to active. However, it does not disclose nuances such as whether intersecting ranges or overlapping rules are affected, or irreversibility beyond the annotation. This is adequate but not rich.

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 compact docstring with the main purpose front-loaded, followed by a structured Args section and a brief Returns note. Every line carries information and there is no redundant or filler text.

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 simple tool with three optional parameters, no output schema, and a destructive annotation, the description covers the essential operational details: what it does, parameter roles, and return type. The only notable omission is clarification of what happens when range_address is omitted (defaults to 'A1'), but this is minor given the low complexity.

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 carries the burden of explaining parameters. It documents each one: workbook (None = active workbook), sheet (None = active sheet), and range_address (A1-style with example). It adds meaningful context beyond the bare schema, though it omits the schema's default of 'A1' for range_address, which is a minor 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?

The description uses a specific verb ('Remove') and a clear resource ('all conditional formatting rules from a range'), making the tool's intent unambiguous. The wording also distinguishes it from siblings like add_conditional_format_rule and list_conditional_format_rules, which clearly perform different operations.

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 when to use the tool—whenever the user wants to delete conditional formatting rules from a range—but it provides no explicit guidance on alternatives or exclusions. There is no mention of preferring this over clear_range or checking existing rules with list_conditional_format_rules first.

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