Mitmdump Replay

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'replay flows', without mentioning side effects (e.g., does it start a proxy? does it block? does it modify anything?), whether it is destructive, or what the return value looks like. For a tool that likely launches a long-running process, this is a significant gap.

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, concise sentence that gets to the point, so it is not verbose. However, it lacks any structure (e.g., no separate lines for behavior, parameters, or examples) and is under-specified. It is appropriately short but does not earn its place beyond stating the core function.

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?

Given the tool's complexity — a nested 'params' object with many modes, protocols, and optional fields — the description is far from complete. It does not explain how to set up modes, what the save_path does, or what the replay_kill_extra flag controls. Even though an output schema exists, the description does not mention the return value or how the tool interacts with the environment. For a tool with this many configuration options, the description is inadequate.

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% — the description does not mention the 'params' object or any of its nested properties. While the schema itself has some field descriptions, the description adds no meaning beyond the schema. The agent must open the schema to understand even the basic mode parameter, and the description does not compensate for the low coverage at all.

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 action (replay flows) and the resource (mitmdump), and specifies the two replay modes (client -C and server -S) from .mitm files. It distinguishes itself from sibling tools like mitmdump_start or mitm_export_flow by focusing on replay, but does not explicitly name alternatives, so it is not a perfect 5.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., that flows must already exist) or contrast with mitmdump_start or mitm_export_flow. An agent would have no idea whether to pick this over a sibling without additional context.

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