unifi_gen_createtrafficmatchinglist

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no note that without confirm="YES" nothing is applied, no statement about reversibility or required permissions, which is the exact context a create-with-destroy semantics tool needs.

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?

It is short and front-loaded, which is good, but the only content beyond the tool name is the "generated from developer.ui.com/..." provenance string, which is boilerplate rather than agent-useful information. Space that could carry the confirm/dry_run contract is spent on a docs URL.

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?

This is a destructive, non-idempotent write with no output schema and a preview-versus-apply gate in the schema. The description omits the single most important operational fact — that the call is inert unless confirm is set to "YES" — and gives no indication of what the returned preview or created object looks like.

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% and every parameter (body, confirm, dry_run) is documented in the schema itself, so the baseline of 3 applies. The description contributes no additional meaning about the body shape, the three allowed `type` enum values, or how `items` is interpreted.

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 names a verb and resource ("Create Traffic Matching List"), so the basic action is recognizable. But the second half is only a provenance URL, and it never distinguishes this from the near-identical sibling unifi_net_create_traffic_list or from unifi_gen_updatetrafficmatchinglist, leaving the agent to guess which family to use.

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, when-not-to-use, or alternative is stated. The schema exposes a confirm/dry_run preview flow, but the description never tells the agent when a preview is appropriate versus when to apply, and never mentions the parallel unifi_net traffic-list tools.

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