export_json

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

The description discloses file creation/overwrite behavior ('Creates the output file if it does not exist; overwrites if it does'), which is not covered by annotations. Annotations have readOnlyHint: false and destructiveHint: false, but description adds important context about side effects on the output file.

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 two sentences, front-loading the core purpose and adding one key behavioral detail. Every sentence is informative with no redundancy.

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 tool with 4 parameters and no output schema, the description adequately covers purpose and key behavior (file creation). However, it omits details about JSON format structure, error handling, or performance implications. With minimal complexity, it is nearly 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 coverage is 100% with adequate descriptions for each parameter. The description adds minimal extra meaning beyond the schema (e.g., 'export packets' is already obvious from the name). Baseline of 3 is appropriate.

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 'Export packets from a pcap file to a JSON file at output_path', specifying the verb (export), resource (packets), and output format (JSON). It distinguishes from sibling tools like 'summarize_pcap' or 'read_pcap' by focusing on export to JSON.

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 implies usage for converting pcap to JSON but provides no explicit guidance on when to use this tool versus alternatives (e.g., other export formats). No exclusions or when-not-to-use information is given.

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