sheets_add_conditional_formatting

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

The annotations declare idempotentHint and destructiveHint, but the description adds no additional behavioral context. It does not explain whether rules are appended to existing ones, replace them, or how duplicates are handled. The idempotency hint is left uninterpreted, and no side effects, permissions, or rate limits are mentioned.

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 single sentence with no unnecessary words, making it concise. However, it is so terse that it edges toward under-specification, lacking the detail needed to be genuinely useful. It is acceptable in size but not in substance.

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 tool has a very complex input schema and no output schema, yet the description gives only a bare action statement. It fails to explain the rule types, range specifications, behavioral semantics, or return values. Given the complexity, this is critically 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%, and the description provides no information about the parameters beyond their names in the schema. The rules parameter is highly complex with nested structures, and the description does not compensate at all, leaving the agent to rely entirely on the raw schema without any explanatory context.

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 action ('Add') and the resource ('conditional formatting rules to a Google Sheet'). It uses a specific verb and resource that distinguishes this from siblings like sheets_get_conditional_formatting or sheets_format_cells.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, differences from other formatting tools, or scenarios where this should be preferred. The one-line description gives no context for decision-making.

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