analysis_list_tcp_conversations

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds the behavioral trait that the tool internally handles sharkd tap syntax, which is useful but not rich context about return behavior or edge cases. There is no contradiction with annotations.

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, front-loaded sentence that states the core action and a key benefit without any fluff or repetition. It earns its place perfectly.

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?

An output schema exists and annotations are strong, so return values and safety are covered. However, the description omits mention of optional filtering (display_filter) and limit, leaving a gap for agents to understand the full capabilities. It is adequate but not complete.

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, but it provides no information about analysis_session_id, limit, or display_filter. The tool name implies session context, but the description does not clarify the meaning or usage of any parameter.

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 uses the specific verb 'List' with the resource 'TCP conversations', clearly distinguishing it from sibling tools like analysis_list_frames and analysis_list_http_hosts. It also adds a unique benefit (no manual sharkd tap syntax) that further clarifies its scope.

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 phrase 'without requiring manual sharkd tap syntax' gives clear context on when this tool is useful (avoiding manual tap commands), but it does not explicitly name alternatives or provide when-not-to-use guidance. This meets the 'clear context, no exclusions' level.

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