sheets_add_conditional_format

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

With no annotations, the description must disclose behavioral implications, but it only states the action and lists examples. It does not mention whether existing formatting is overwritten, the effect of the bg_color default, permissions required, or what the response contains. The behavioral profile is largely opaque.

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 short sentence, which is concise, but the trailing 'etc.' is vague and adds little structural value. It front-loads the main verb but does not provide organized detail about the rule types or other configuration.

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?

Conditional formatting is a complex feature requiring explanation of rule types, value handling, and range application. The description provides almost no context beyond the tool name itself, and with no annotations or schema explanations, it is severely incomplete for an agent to invoke it correctly.

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 for the rule_type parameter by listing example values, but it fails to explain other required parameters (e.g., values, spreadsheet_id, sheet_id, or row/column indices) or how they interact. This is insufficient for a 9-parameter tool.

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's action ('Add conditional formatting') and lists example rule types, making it distinct from sibling tools like sheets_add_chart and sheets_add_named_range. However, it does not explicitly mention the target spreadsheet or range, so it falls slightly short of a fully scoped purpose.

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 provides no guidance on when to use this tool versus alternatives such as sheets_batch_update or sheets_add_sheet. There is no mention of prerequisites, typical scenarios, or exclusions, leaving the agent without context for tool selection.

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