unifi_get_traffic_matching_list

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

Annotations already mark the tool as readOnlyHint=true and destructiveHint=false, so the description adds only minor context by noting that the response contains the 'full items array'. No mention of rate limits, permissions, or other behavioral traits beyond what is implied by 'Get'.

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 a single, front-loaded sentence with no extraneous words. It efficiently conveys the essential action and scope, though it could be slightly expanded to include usage hints without sacrificing conciseness.

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?

Given the tool's simplicity, two required parameters, and presence of an output schema, the description is adequate but lacks context about when to use this vs. other list tools. It does not explain what a traffic matching list is or how the ID relates to other operations, leaving gaps for a new agent.

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?

The input schema covers 100% of parameters with clear descriptions for `siteId` and `trafficMatchingListId`. The description does not add any additional semantic value beyond what the schema already provides, so it meets the baseline without improvement.

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 action ('Get') and the resource ('a specific traffic matching list by ID'), distinguishing it from sibling tools like `unifi_list_traffic_matching_lists`, which retrieves all lists. The mention of '(full items array)' further clarifies the scope of the returned data.

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?

The description implies usage when you have a specific ID, but it does not explicitly contrast with list tools or explain when not to use it. No context is provided for prerequisites or alternatives, making it minimally adequate.

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