export-sessions-pcap

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

The description discloses that the PCAP is saved to a temporary directory and only the file path is returned. However, it does not cover file lifetime, size limits, or potential errors. Since no annotations exist, the description carries the full burden and falls short.

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 three sentences and a short instruction. It is front-loaded with the primary purpose and contains no superfluous information. Every sentence adds value.

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?

Without an output schema, the description correctly states that the return is a file path. It lacks details on file naming, expected size, or behavior for large queries. Adequate but incomplete for the parameter count.

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 baseline is 3. The description adds minimal value beyond the schema, only providing an example for the query parameter. No additional meaning for other parameters.

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 states the tool exports a PCAP file for multiple GreyNoise sensor sessions matching query criteria. It distinguishes from the sibling tool get-session-pcap, which handles single sessions.

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 explains the query syntax but does not explicitly state when to use this tool vs alternatives like get-session-pcap. Usage guidance is implied but not directly provided.

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