add_conditional_format

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

With no annotations, the description must disclose behaviors. It states the format applies when true but omits side effects (e.g., overwriting existing rules), parameter effects (bold, colors), and idempotency. Minimal behavioral disclosure beyond obvious.

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?

Two-sentence description is front-loaded with purpose, then explains key parameters. Concise with no wasted words. Could use more structure (e.g., list) but effective.

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?

Given 7 parameters, no annotations, and no output schema, the description is incomplete. Missing parameter explanations, return value, error conditions, and sibling differentiation. Does not fully equip an agent to invoke 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 coverage is 0%, so description must compensate. It explains condition_type and values well (2 of 7 params), but ignores bold, range, text_color, spreadsheet_id, background_color. Only 28% of parameters are meaningfully described.

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 adds a conditional-format rule to an A1 range, specifying verb and resource. However, it does not explicitly differentiate from sibling tools like update_conditional_format, which lowers the score from 5 to 4.

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 vs alternatives, no prerequisites (e.g., spreadsheet must exist), and no exclusions. It only explains condition types without usage context.

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