delete_traffic_matching_list

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the delete action but omits critical details such as whether the deletion is permanent, whether related data is affected, permission requirements, or error conditions. This is a significant gap for a mutating operation.

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 concise and well-structured with no wasted words. It fronts the core action, then provides parameter details in a clean line-by-line format, making it easy to parse.

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?

While the parameter guidance is strong and an output schema exists, the lack of behavioral context (e.g., irreversibility, permissions, side effects) makes the description incomplete for an agent deciding whether deletion is safe and appropriate. For a simple delete operation, this is acceptable but not thorough.

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 schema provides only type strings with 0% description coverage. The description compensates fully by explaining that host can be a name, ID, or composite ID, site can be a name or ID, and list_id is required and obtainable from the specific list endpoint. This gives an agent all necessary parameter semantics.

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 starts with 'Delete a traffic matching list', which clearly states the action (delete) and the resource (traffic matching list). This distinguishes it from sibling tools like create_traffic_matching_list and list_traffic_matching_lists, so an agent can infer the operation without ambiguity.

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 explains how to obtain the required list_id (from list_traffic_matching_lists) and provides format details for host and site. It does not explicitly state when to use this tool over alternatives, but the 'delete' verb makes the use case obvious in the context of the sibling CRUD tools.

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