excel_conditional_formatting

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Apply conditional formatting,' implying a write/mutation operation, but doesn't clarify permissions, side effects (e.g., overwriting existing formatting), or error handling. This is inadequate for a tool that modifies data without safety annotations.

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, efficient sentence with no wasted words. It's front-loaded and to the point, though it could be more informative. The brevity is appropriate but borders on under-specification given the tool's complexity.

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 the complexity (3 parameters, nested rules object, no annotations, no output schema), the description is incomplete. It doesn't explain the input structure, expected behavior, or output, leaving significant gaps for the agent to infer usage. This is inadequate for a mutation tool with undocumented parameters.

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 schema provides no parameter details. The description mentions 'range' but doesn't explain the three required parameters (worksheetName, range, rules) or their semantics (e.g., format of range, structure of rules). It adds minimal value beyond the schema, failing to compensate for the coverage gap.

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 'Apply conditional formatting to a range' clearly states the action (apply) and target (conditional formatting to a range), but it's vague about the scope and lacks differentiation from sibling tools. It doesn't specify what 'conditional formatting' entails (e.g., rules, styles) or how it relates to Excel operations, making it less specific than ideal.

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. The description doesn't mention prerequisites, such as needing an open workbook or specific worksheet, nor does it differentiate from other Excel tools like excel_data_validation or excel_write_worksheet. This leaves 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.