Mitmweb Get Flow Detail

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

With no annotations, the description carries the behavioral burden. It does disclose a useful behavioral trait ('automatic secret redaction') and the kind of data returned, but it doesn't explicitly state that the operation is read-only, whether a session must be active, or any limits on payload size/content views.

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?

A single, front-loaded sentence contains no filler or repetition, and every phrase adds information about scope, contents, and redaction behavior.

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 an output schema that documents return values and a nested input schema, the description is reasonably complete for selection, but it lacks guidance on when to use it and how the optional parts/content_view/redact options affect the result, which matters at 0% schema description coverage.

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%, so the description must compensate. It partially does by linking 'headers, payloads' to flow content and 'content views' to the content_view parameter and 'secret redaction' to redact, but it doesn't explain required session_id/flow_id semantics or the parts/redact/content_view interplay in detail.

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 uses a specific verb ('Fetch') and a specific resource ('detailed inspection data for a single flow from mitmweb'), and lists included content (headers, payloads, content views). This clearly differentiates it from the sibling mitmweb_get_flows, which lists flows, by emphasizing a single flow.

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 use for inspecting one flow but never states when to reach for this tool versus alternatives such as mitmweb_get_flows, mitm_export_flow, or filter tools. It also provides no exclusion criteria or explicit precondition like needing an active mitmweb session.

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