remove_tablix_filter

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

Describes the behavioral detail that removing the last filter drops the empty '<Filters/>' block, which is valuable given no annotations. However, it does not disclose potential side effects, permissions, or return behavior.

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 compact sentences. First sentence states the core purpose; second sentence provides essential usage guidance and a behavioral note. No redundancy or unnecessary information.

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?

Adequate for a simple removal tool, but lacks information on return values, error cases, or confirmation of removal. No output schema is provided. Given the complexity of sibling tools, it could be more 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?

The description does not elaborate on the three parameters beyond the schema. 'filter_index' is implied to be the index, but no details on format or relation to other parameters. Schema coverage is 0%, so the description fails to add value.

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?

Explicitly states the action (remove) and resource (filter by index). Distinguishes from sibling tools like 'remove_dataset_filter' by specifying 'tablix_filter'. Includes context about RDL anonymity, reinforcing the specific use case.

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?

Provides a clear precondition: use 'list_tablix_filters' to find the correct index. Does not explicitly state when not to use or mention alternative methods, but the context is sufficient for proper usage.

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