Create traffic matching list

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is partly covered. However, for a destructive create the description says nothing about side effects, what the confirm/dry_run preview flow yields, or what dependencies (firewall policies) the new list may affect, and it defers the payload contract to 'Network API docs'.

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 with the action front-loaded and no filler. The second sentence is arguably low-value boilerplate that points away from the description rather than adding content.

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 is a destructive create with an untyped 'body' object, zero required parameters and no output schema, so the description carries real weight — yet it never states what the body must contain, what a preview response looks like, or what happens on success. Delegating the payload contract to external docs leaves the agent under-equipped.

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%, so 'confirm' and 'dry_run' semantics are already documented in the schema. The description's only parameter-related contribution is pointing at Network API docs for the opaque 'body' object, which adds a reference but no concrete shape, required fields, or examples.

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 and resource ('Creates a new traffic matching list') and scopes it to 'the current site', so the action is unambiguous. It does not distinguish itself from the near-identical sibling unifi_gen_createtrafficmatchinglist or from unifi_net_update_traffic_list.

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 on when to use this versus the duplicate generative sibling or the update/delete traffic-list tools, and no prerequisite or ordering advice. The only implicit context is that the list is created on the current site.

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