Manage Conditional Formatting

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds that the tool supports delete operations, which is consistent with the annotations, but offers no additional side-effect context such as behavior on missing rules or replacement semantics.

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 one clear sentence, front-loaded with the primary purpose, and immediately enumerates the three operations. There is no filler or redundant wording.

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 an output schema present and thorough annotations, the description need not explain return values or safety. It provides enough high-level context for a complex tool, though it could mention distinctions from nearby formatting tools. Overall, it is adequate given the structured data available.

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 100%, so the description does not need to explain parameters. It adds no extra parameter semantics beyond the schema; the baseline of 3 applies because the schema does the heavy lifting.

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 tool 'manages conditional formatting rules on a Google Sheet' and enumerates the supported operations: adding, updating, and deleting. This specific verb+resource combination distinguishes it from sibling tools like format_sheet_range, which handles other formatting aspects.

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 use for conditional formatting rule management but provides no explicit when-to-use guidance or alternatives. It does not mention when to prefer this tool over format_sheet_range or other sheet-modification tools, leaving the agent to infer context from the name and operations.

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