flow_replay

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

No annotations provided, so description carries full burden. It does not disclose any behavioral traits such as side effects (does it modify state?), safety (idempotent?), or requirements. 'Replay' implies action but no details on what happens.

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 short sentence, which is concise but lacks essential details. It is not front-loaded with critical information; it is minimal but not optimally structured.

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 two parameters and an output schema, the description is insufficient. It does not explain the replay process, preconditions (e.g., proxy status), or what the output contains. The output schema exists but description adds no value.

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?

Parameters are not described at all. Schema description coverage is 0%, and the tool description does not explain what 'flow_id' or 'use_modified' mean. The default for 'use_modified' is mentioned but not its effect.

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 a captured flow') and specifies the resource ('captured flow') and method ('using mitmproxy's built-in replay.client'). It distinguishes from sibling tools that create, delete, get, etc., by focusing on replaying.

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?

No guidance on when to use this tool versus others. No mention of prerequisites or context (e.g., proxy must be running, flow must be captured). The description is purely functional without any usage direction.

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