unifi_list_traffic_matching_lists

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

With no annotations, the description carries full burden for behavioral disclosure. It says 'list all' but does not mention pagination, rate limits, or whether the operation is read-only. The input schema implies pagination via limit/offset, but the description fails to confirm this behavior.

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?

The description is extremely concise at 9 words. It is front-loaded with the core action. However, it could add a touch more detail without losing conciseness, such as mentioning pagination or return format.

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?

No output schema exists, so the description should explain the return value. It does not describe what a traffic matching list contains or that the response is a list of objects. The lack of return value context makes it incomplete for agent decision-making.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema's descriptions for limit, offset, and filter. The parameters are self-explanatory from the 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?

The description clearly states the verb 'List', the resource 'traffic matching lists', and adds context as 'reusable traffic pattern definitions'. It effectively distinguishes from sibling tools like unifi_get_traffic_matching_list and unifi_list_traffic_routes.

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 tool versus alternatives. It simply states the action without context about scenarios or exclusions. The description does not mention when to use this list tool instead of the get tool for a specific list.

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