add_slicer

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits (defaults to Dropdown, mode changes the visual style) but does not mention side effects, response behavior, or prerequisites like an open report session. It is honest but incomplete for a mutation tool.

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 sentences, front-loaded with the core action, no redundancy. Every clause adds meaning.

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?

For a tool with 11 parameters and no output schema, the description covers the primary behavior and mode options but omits return value, error conditions, and explicit guidance for other parameters. It is adequate but not comprehensive.

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 descriptions cover only 18% of parameters (kind and mode). The description fills this gap for the most behaviorally significant parameters: it explains mode values (Dropdown, List, Between, Single) and distinguishes column vs measure. It does not explain x/y, width/height, or title, but these have sensible defaults and are less critical.

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 action ('Add a slicer') with a specific object ('one column or measure'). It also explains the default mode and how to request alternatives, distinguishing it from sibling tools that manage slicers rather than create them.

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 implies when to use different modes (Dropdown is default and recommended, List for classic vertical list, Between/Single for ranges) but does not explicitly compare this tool to sibling slicer tools like set_slicer_selection or fix_slicer_single_select. No exclusions or alternative tool references.

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