delete-viz-filter

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

There are no annotations, and the description only states 'Delete a visualization filter.' It does not disclose whether deletion is permanent, whether dependencies are affected, or any required permissions. This is minimal disclosure 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?

The description is a single sentence that directly states the tool's purpose. It contains no unnecessary words and is appropriately sized for a simple delete operation.

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 tool has no annotations, no output schema, and an undocumented parameter. The description is too brief to provide sufficient context for an agent to confidently invoke it, especially with no explanation of the parameter or side effects.

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 description coverage is 0%. The description does not explain the meaning or format of 'filter_id', and the input schema only provides its type. The description adds no value beyond the schema.

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 states the verb 'Delete' and the resource 'visualization filter', which clearly identifies the tool's core function. It is clear but does not explicitly differentiate from the sibling tool 'delete-viz-filters-bulk' or mention it deletes a single filter.

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?

No guidance is provided on when to use this tool versus alternatives like 'delete-viz-filters-bulk' or 'update-viz-filter'. The usage context is only implied by the tool name and description.

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