get-session-pcap

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

Describes that the file is saved to a temporary directory and can be opened with common tools, which is helpful. However, with no annotations, it fails to disclose potential side effects like file size limits, deletion of temp files, or authentication/rate limits.

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?

Two sentences, directly stating purpose, output format, and typical usage. No unnecessary words; front-loaded with critical information.

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 simple file download tool with no output schema, the description adequately explains what the output is (file path) and how to use it. It lacks mention of error handling or edge cases, but overall sufficient.

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 coverage is 100%, so the baseline is 3. The description does not add additional parameter semantics beyond what the schema already provides; it only explains the overall function.

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?

Clearly states the tool downloads a raw PCAP capture for a single GreyNoise sensor session. It specifies the output is a binary PCAP file saved to a temp directory and returns the file path. However, it does not explicitly differentiate from the sibling tool export-sessions-pcap, which likely handles bulk exports.

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?

Implies usage for downloading a single session's PCAP, but no explicit guidance on when to use this tool versus alternatives like export-sessions-pcap. No prerequisites or exclusions are mentioned.

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