unifi_get_traffic_matching_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), which implies it's non-destructive, but doesn't mention authentication requirements, rate limits, error conditions, or what happens if the ID doesn't exist. This leaves significant gaps for a tool that presumably interacts with network infrastructure.

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, efficient sentence that communicates the core purpose without any wasted words. It's appropriately front-loaded with the essential information.

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 tool that retrieves specific network configuration objects with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'traffic matching list' is, what information it returns, or provide any context about the Unifi system it operates within. The agent would need to guess about the return format and system context.

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 has 100% description coverage, with both parameters clearly documented as 'Site ID' and 'Traffic matching list ID'. The description doesn't add any meaningful semantic context beyond what the schema already provides, such as explaining what these IDs represent or where to find them.

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'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'unifi_list_traffic_matching_lists', which would retrieve multiple lists rather than a specific one.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling 'unifi_list_traffic_matching_lists' for retrieving multiple lists, nor does it explain prerequisites like needing to know the specific ID beforehand.

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