Get traffic matching list

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing on top: no mention of what happens with an unknown id, whether the id is a UUID or a name, or what a traffic matching list contains. With annotations present the bar is lower, but zero added context still only earns a 2.

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?

It is short and front-loaded with no waste, but the brevity comes from under-specification rather than efficiency — a six-word fragment that lacks a verb. It could easily carry one more clause (identifier source, return shape) without becoming verbose.

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?

The tool is simple (one required param, no output schema), which limits how much is needed, but the description still leaves the identifier semantics and the returned record's nature unaddressed. For a getter reachable from a large sibling set, this is thinner than an agent needs to call it confidently.

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 `id` parameter, so the description carries the full burden — and it says nothing about which identifier is expected. An agent cannot tell from either source whether `id` is the internal UUID from the list endpoint or a human-readable list name.

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?

"Detail for one traffic matching list" names the resource and implies a single-record fetch, so an agent can guess it returns one list rather than a collection. But it is a noun phrase with no verb, and it never names its sibling list_traffic_lists/update_traffic_list to sharpen the distinction. Purpose is inferable, not stated.

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 guidance, no prerequisites (e.g. needing an id from unifi_net_list_traffic_lists first), and no alternatives named. The agent must infer that this is the follow-up call to the list tool for a single item.

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