Manage Conditional Formatting

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

Annotations already indicate destructive and non-read-only behavior. The description adds that deletion is supported and that the tool consolidates add/update/delete operations, but it does not disclose side effects, auth requirements, or action-specific consequences beyond what annotations provide.

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 two short sentences with no filler. The first sentence establishes the resource and the second enumerates the operations, making the purpose immediately clear and front-loaded.

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 11 parameters and three distinct actions, the schema carries the detailed operational load very well, and an output schema exists so return-value explanation is unnecessary. The description could add a brief usage-selection note, but combined with the rich schema it is largely sufficient for correct invocation.

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%, and each parameter description already documents action-specific requirements such as rule_index being required for update/delete and range_name being required for add. The tool description itself adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 names a specific resource—conditional formatting rules on a Google Sheet—and clearly enumerates the supported operations: adding, updating, and deleting. This distinguishes it from general formatting tools like format_sheet_range and avoids being a mere restatement of the tool name.

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 the use case by focusing on conditional formatting rules, but it never explicitly says when to prefer this tool over alternatives or when not to use it. It states what the tool does but provides no exclusions or sibling-tool comparisons.

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