unifi_gen_gettrafficmatchinglist

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds nothing beyond that: no statement of what a 404 / unknown ID returns, no note that the ID is a UUID that must come from the list endpoint, no mention of response shape.

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 terse line, front-loaded with the verb and resource, so there is no padding. However, brevity here reflects under-specification rather than editorial economy, and the 'generated from ...' URL adds provenance but no decision-relevant 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 read-by-ID tool with annotations and no output schema, the agent still needs to know what entity is returned, that the UUID must be sourced elsewhere, and how this differs from the list sibling. None of that is present, leaving the definition materially incomplete.

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 the single required parameter trafficMatchingListId. The schema supplies the uuid format and regex, but the description gives no hint that this ID is a traffic-matching-list identifier obtained from the list endpoint, so it fails to compensate for the coverage gap.

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 restates the tool name ('Get Traffic Matching List') and appends a documentation URL; it never says it retrieves a single traffic-matching list identified by UUID, nor distinguishes it from the sibling unifi_gen_gettrafficmatchinglists list endpoint. This is essentially tautology plus provenance.

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 when-to-use, when-not-to-use, or alternative is named. An agent cannot tell from the text whether to call this versus unifi_gen_gettrafficmatchinglists or unifi_net_get_traffic_list; it must infer everything from the function name alone.

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