xlsx_conditional_formats

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds context: lists output contents (range, type, operator, formulae, priority, stopIfTrue) and mentions a per-type tally, plus notes the tool counts against a monthly cap. No contradictions with 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 well-structured with clear sections (list of rules, uniqueness claim, USE WHEN, DO NOT USE WHEN). It is slightly verbose but each sentence adds value. Could be more concise but not overly long.

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 description covers the tool's output (per-rule details, tally) and usage contexts well, but lacks parameter documentation. No output schema exists, so the description should compensate by explaining expected input (file_b64, options) but does not. Additionally, it does not explain error conditions or file size limits beyond the 10k cap.

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 has 2 parameters (file_b64, options with limit/sheet) with 0% description coverage. The description provides zero information about these parameters: no explanation of file_b64 (base64-encoded file), limit, or sheet. The agent is left guessing parameter meaning and constraints. Severe 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 clearly defines the tool's purpose: listing every conditional formatting rule in a workbook, specifying rule types (color scales, data bars, icon sets, etc.) and per-rule details. It explicitly distinguishes itself from siblings by noting that pandas drops conditional formatting and openpyxl lacks rollup/classification, making the tool unique.

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 explicit USE WHEN and DO NOT USE WHEN sections, citing specific audit/scenario contexts (e.g., auditing dashboards, extracting business rules) and alternatives (use xlsx_read for cell values, xlsx_write cannot re-apply CF rules). Also notes the free tier cap (10k/mo). Excellent guidance.

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