wireshark_merge_pcaps

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

Description adds minimal behavioral context beyond the destructiveHint annotation. Does not disclose whether output file will be overwritten, required file permissions, or error handling.

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?

Extremely concise—one sentence plus a fragment. Every word earns its place, but structure could be improved (e.g., separating parameter details into a list).

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?

No output schema and limited parameter documentation. Missing important context: file format requirements, size limits, behavior if input files don't exist, and typical use cases.

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?

Input_files parameter gets partial description ('comma-separated paths') but output_file is entirely unexplained. With 0% schema coverage, description should compensate more for the missing 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 'Merge multiple capture files into one' is a clear, specific verb+resource statement that distinctly identifies the tool's function compared to sibling tools like wireshark_editcap_split.

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 guidance on when to use this tool instead of alternatives or prerequisites. The description only provides parameter format ('comma-separated paths') without context for usage decisions.

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