get-viz-filters

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 merely states 'List all visualization filters' and reveals nothing about pagination, ordering, return structure, or potential side effects. There is no context about read-only behavior, permissions, or data scope, leaving the agent with minimal understanding beyond the basic action.

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 concise sentence, front-loaded with the action and resource. It contains no fluff, redundancy, or irrelevant information, earning a perfect score for conciseness.

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 simple list-all tool with no parameters, no annotations, and no output schema, the description is adequate but minimal. It clearly conveys the primary function, but lacks any detail about return values or behavioral constraints. Given the lack of supporting structured data, this is a minimum viable description that leaves some gaps.

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 tool has zero parameters, so the baseline is 4. The description doesn't need to explain any parameters since the schema is empty. It correctly focuses on the operation itself, adding no unnecessary parameter details.

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 uses a specific verb ('List') and resource ('visualization filters') with an explicit scope ('all'), which clearly distinguishes it from the sibling tool 'get-viz-filter' that likely retrieves a single filter. This is a clear and non-tautological purpose.

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 word 'all' implies this tool is for listing every visualization filter, contrasting with 'get-viz-filter' for a single one. However, it doesn't explicitly state exclusions or alternatives, so it falls short of a 5. It provides clear context without explicit when-not guidance.

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