Delete traffic matching list

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

Annotations already declare destructiveHint=true and idempotentHint=true, so "IRREVERSIBLE" is reinforcement rather than new information (and is consistent with the annotations). The description does say nothing about the preview/confirm gate, which is the single most important behavioral trait here, nor about auth requirements.

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 short sentences, front-loaded with the verb and the destructive warning — no filler. It is efficient, though the brevity comes at the cost of the missing safety-flow detail rather than being truly complete.

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 destructive, open-world delete with no output schema and an undocumented required parameter, the description should explain the confirm/dry_run preview cycle and what breaks when a traffic matching list is removed (e.g. references from firewall policies). Neither is present.

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?

All three parameters are ignored in the description, and schema description coverage is only 67% (the `id` parameter has no description at all). The description does not compensate by explaining that `id` is the list identifier and that `confirm`/`dry_run` gate execution, so half the invocation semantics rest on an undocumented 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?

States a specific verb+resource ("Deletes a traffic matching list") that is unambiguous and correctly implies mutation. It does not distinguish itself from the sibling unifi_net_update_traffic_list or the generated unifi_gen_deletetrafficmatchinglist variant, so an agent gets no differentiation signal.

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 when-to-use guidance, no prerequisites, and no mention of the two-step flow that the schema implies (preview without `confirm`, then apply). An agent must read the schema to discover that calling without confirm="YES" is a safe preview.

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