delete_filter_group

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

Annotations only declare destructiveHint=true generically. The description adds real behavioral context: what actually breaks (data displayed in affected visuals changes) and that a backup is automatically created before deletion. That is meaningful disclosure beyond the annotation.

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?

Three tight lines: purpose first, then a bolded WARNING, then the mitigating backup fact. Every sentence earns its place and the destructive nature is front-loaded.

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?

An output schema exists so return values need no explanation, and the description covers impact and backup behavior. It stops short of noting permissions or recovery path for the backup, which would complete the picture for a destructive operation.

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 100% with only two simple string params, so the description correctly does not duplicate them. However, it adds no extra meaning about ID sources or format, so baseline 3 applies.

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?

States a specific verb (Delete) and resource (filter group) scoped to a QuickSight analysis, which separates it cleanly from sibling add_filter_group and from delete_visual/delete_parameter. An agent knows exactly what object type is being removed.

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?

Usage is implied by the destructive warning, but the description never states when to delete versus alternatives (e.g., disabling or editing the filter group, or whether backup_analysis should be run first). No explicit when-not guidance is given.

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