wireshark_editcap_deduplicate

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating operation. The description usefully adds the sliding-window semantics and the default of 5 packets, which is behavior not encoded anywhere else. However, it omits key behavioral facts for a destructive tool: whether output_file is overwritten if it exists, and whether the input is left untouched.

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 front-loaded sentence with no filler; the core action and its default are stated immediately. It is lean to the point of under-specification, but nothing in it is wasted.

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, file-writing tool with no output schema and 0% parameter documentation, the description should cover output file behavior, overwrite semantics, and the relationship to the other editcap tools. It provides only the window default, leaving an agent to guess the rest.

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% and the description only clarifies one of three parameters (duplicate_window, including its default). The semantics of input_file and output_file — notably whether output_file is created or overwritten — are left entirely to inference, so the description does not 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 states a specific verb and resource ('Remove duplicate packets') plus the mechanism ('sliding window'), so an agent knows exactly what operation is performed. It does not explicitly contrast itself with the close siblings wireshark_editcap_trim, wireshark_editcap_split, or wireshark_editcap_time_shift, so it falls short of full sibling differentiation.

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?

There is no guidance on when to prefer this tool over the other editcap-family tools or over merge/aggregate operations. No prerequisites, no exclusions, no mention of when deduplication is appropriate (e.g., after capture merge).

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