clear_traffic

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

With no annotations provided, the description carries the full burden of disclosing effects. It clearly states that the action 'permanently deletes all recorded flows' and adds the important caveat that 'Session variables are NOT cleared.' This gives the agent a complete picture of the destructive and non-destructive aspects.

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 extremely concise, with a direct action statement followed by a clear usage scenario and a prominent warning. Every sentence earns its place, and there is no wasted text.

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 parameterless, destructive tool, the description covers the purpose, the recommended usage time, and the key behavioral caveat about session variables. Since an output schema exists, return-value details are unnecessary, making this description complete for its complexity.

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 tool takes zero parameters and the schema is empty, so there are no parameters for the description to explain. The description correctly avoids adding irrelevant parameter details, earning the baseline score for parameterless tools.

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 uses the specific verb 'Delete' with a clear resource: 'all captured traffic from the database.' It distinguishes itself from sibling read tools like get_traffic_summary and search_traffic, making its scope unambiguous.

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 explicitly states when to use it: 'Use when you want a clean slate before a new test.' It also warns that session variables are not cleared, which implies a limitation, but it does not name an explicit alternative tool for clearing session variables.

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