unifi_delete_traffic_matching_list

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. 'Delete' implies a destructive mutation, but it doesn't disclose whether this requires admin permissions, if deletion is permanent/reversible, what happens to dependent rules, or typical error cases. The description adds no context beyond the basic action.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and appropriately sized for a simple delete operation.

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 destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'traffic matching list' means in context, the impact of deletion, required permissions, or what the tool returns. Given the complexity of network management tools, more contextual guidance is needed.

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 100%, with both parameters ('siteId', 'trafficMatchingListId') clearly documented in the schema. The description adds no additional parameter context beyond what the schema provides, so the baseline score of 3 is appropriate given the schema does the heavy lifting.

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 ('Delete') and the resource ('a traffic matching list'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'unifi_delete_acl_rule' or 'unifi_delete_firewall_zone', but the specificity of 'traffic matching list' provides inherent distinction.

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 prerequisites (e.g., needing an existing traffic matching list), consequences of deletion, or relationships with sibling tools like 'unifi_get_traffic_matching_list' for verification or 'unifi_create_traffic_matching_list' for recreation.

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