get_flow_packets

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

No annotations are supplied, so the description carries the behavioral disclosure burden. It discloses the return contract (normalized flow type and ID, generated display filter, packet count, truncation flag, packet summaries) and the special TLS/HTTP matching rule. The verb 'Retrieve' implies read-only behavior, though the description does not explicitly state the absence of side effects.

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 compact and logically organized: a clear lead sentence, a short context paragraph for flow ID semantics, then Args and Returns sections. Every sentence contributes useful information with no filler or restatement of the schema.

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 retrieval tool with no annotations and a bare schema, the definition covers parameter semantics, valid values, constraints, return fields, and an important edge case for TLS/HTTP flows. It omits explicit guidance about when to prefer sibling tools, but that gap is minor given the clarity of the primary purpose and contract.

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 Args section fully compensates: capture_id is defined as a currently loaded capture, flow_type lists all valid values, flow_id is explained as a non-negative TShark stream identifier, and limit is given a 1-1000 range. This adds meaning well beyond the bare schema, especially the flow-ID-versus-port distinction.

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 opening sentence names the exact action and resource: 'Retrieve packets belonging to a decoded transport or application flow.' It further clarifies that flow IDs are TShark stream identifiers, not port numbers, and enumerates supported flow types, which separates it from general packet-retrieval siblings.

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 gives clear operational context: valid flow types are listed, limit is bounded, and TLS/HTTP flows require the selected application protocol to be present on the packet. However, it never explicitly tells an agent when to choose this tool over siblings such as filter_packets, get_packets_by_time_range, or get_related_packets; the intended usage is implied rather than stated.

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