run_tshark_command

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

No annotations are provided, so the description must carry the safety/behavior context. It states the tool executes tshark and returns output, but does not disclose potential side effects (e.g., file writes, capture activity), shell interpretation/quoting, privileges, or error handling. This is a meaningful gap for a command-execution tool.

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 brief and structured with Args/Returns, containing no filler. It is appropriately sized but not excessively terse, and the Returns section is useful.

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?

Given the tool's power as a raw command runner and the existence of many specialized alternatives, the description is incomplete: it lacks usage guidance, failure behavior, security caveats, and exact return semantics. The output schema helps but does not cover these.

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 has 0% description coverage, and the tool description's Args line adds only 'The command line arguments to pass to tshark', which largely restates the property name. It does not specify how multiple arguments are delimited, whether quoting is required, or whether shell features are available. Critical details for correct invocation are missing.

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 identifies the action: run a TShark command with user-supplied arguments. It uses a specific verb and resource, but does not explicitly distinguish this raw wrapper from the many specialized tshark sibling tools.

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 use this instead of the specialized siblings (follow_stream, analyze_pcap_file, etc.), nor any exclusions or prerequisites. The only hint is 'with the given arguments,' implying a generic escape hatch, but not stated.

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