Mitmweb Start

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Start an interactive session' hints at a long-running side effect, but it does not mention whether the command blocks, returns immediately, requires cleanup, changes network settings, or must be paired with mitmweb_stop. The web UI/REST API note adds some context, but major behavioral gaps remain.

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, efficiently worded sentence with no filler. It front-loads the core action and key features. While it is too short for the tool's complexity, the conciseness itself is well handled.

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 high complexity of the nested params schema, multiple modes, and many sibling tools, this description is incomplete. It omits when to use the tool, what the interactive session implies for lifecycle management, security-relevant options like web_password, and how this differs from mitmdump_start. An output schema exists, but that does not compensate for missing operational context.

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?

The schema description coverage is 0%, and the description adds no parameter-level meaning. It does not mention the required nested mode array, scripts, web host/port, save path, or listen host. The input schema has detailed types and enums, but the description does not compensate for the lack of top-level parameter explanation.

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 and resource: 'Start an interactive mitmweb proxy session'. It also highlights distinguishing features, 'web UI and REST API bridge enabled', which separates it from sibling tools like mitmdump_start and the stop/query tools.

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 is given on when to use this tool versus alternatives such as mitmdump_start, or when a session already exists and should be stopped. The description only implies 'start mitmweb' without any conditions, prerequisites, or exclusions.

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