set_slicer_conditional_formatting

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

With no annotations, the description carries the behavioral disclosure burden. It includes a useful instruction to 'Verify the render in Desktop', implying changes may not be immediately visible, and explains the target and rule format. However, it does not disclose whether existing formatting is overwritten, what happens on invalid input, or whether the operation is reversible.

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 compact, uses a clear front-loaded purpose statement, and provides essential details in a few sentences. Every sentence adds value: purpose, target/rules syntax, and a verification note. No redundancy or fluff.

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 core operation, key parameters, and a post-requisite verification step. It is reasonably complete for a moderately complex tool, though it omits edge-case details like overwrite semantics or prerequisites on the slicer having a measure. Overall, it provides enough context for a competent agent to use the tool correctly in typical scenarios.

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?

The schema already covers 86% of parameters with descriptions. The description repeats the target and rules formats (fill|font|callout and {min,max,color} bands) that are present in the schema, adding little new semantic information. Thus it meets the baseline but does not elevate it.

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 a specific action and resource: 'Apply measure-driven conditional formatting to a SLICER or button-slicer.' It further distinguishes itself from related tools by noting it 'generalises the table/matrix FillRule builders' and listing target options (fill|font|callout), making its scope unambiguous.

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 clearly indicates the tool is for slicer/button-slicer conditional formatting, which contrasts with table/matrix builders. It gives a clear use case but does not explicitly mention when not to use it or name alternative tools, so it lacks explicit exclusions.

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