unifi_gen_gettrafficmatchinglists

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — it does not mention pagination behavior, default result count, or what a 'traffic matching list' contains.

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?

A single short line, front-loaded with the operation, which is good. But the trailing 'generated from developer.ui.com/...' provenance adds no actionable value for an invoking agent, and the brevity reflects under-specification rather than economy.

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 paginated list endpoint with no output schema and three undocumented parameters, the description should explain pagination and filtering. It supplies none of that, so an agent cannot confidently page or filter results.

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% for three parameters (limit, filter, offset), so the description carries the full burden and fails to compensate. It never explains filter syntax, maximum page size, or offset semantics, leaving the agent to guess at how to page or filter.

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 ('List') and resource ('Traffic Matching Lists'), so the agent knows the operation type. However, it does not distinguish itself from the sibling unifi_gen_gettrafficmatchinglist (singular) or explain how these lists differ from unifi_net_list_traffic_lists, leaving ambiguity about which list tool to pick.

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 singular gettrafficmatchinglist sibling or the net_* traffic list tools. There are no prerequisites, exclusions, or selection criteria stated — only a documentation URL.

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