analyze_tcp_conversation

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

With no annotations, the description carries the behavioral disclosure burden. It usefully states that findings are evidenced by frame numbers, but it does not explicitly confirm the operation is read-only, describe failure behavior, or mention any prerequisites beyond the two parameters.

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 a single dense, front-loaded line with no filler. Every phrase contributes substantive information about what the tool analyzes and how results are presented.

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?

The description covers key outputs and the single-conversation scope, but with no output schema and no annotations it leaves gaps: how to source stream_id, whether the file must already be loaded, and what error conditions exist. It is adequate for selection but not fully sufficient for invocation without relying on external knowledge.

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%, so the description must compensate for the undocumented file_path and stream_id parameters. It only hints that a single TCP conversation is involved, offering no detail on what stream_id represents, how to obtain it, or accepted file path formats.

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 tool's focus: RTT, retransmissions, zero-window events, and duplicate ACKs for a single TCP conversation. Though it lacks an explicit verb, the scope is specific and distinguishable from siblings like list_tcp_conversations or detect_security_anomalies.

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 is given for when to choose this tool over alternatives, nor any mention of prerequisites such as first listing available TCP conversations or obtaining a stream_id. The intended use is only implied by the tool name and contents.

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