Mitmdump Stop

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

With no annotations, the description is responsible for flagging mutating behavior; it does state that the session is stopped and ports are released. However, it does not mention graceful-stop vs force-kill semantics, whether the call is reversible, or what happens if the session is already stopped.

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?

One tight sentence with no filler; the action and resource are front-loaded, and 'release ports' is a valuable second clause. It earns its place.

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?

Although an output schema exists and the input schema documents the session ID, the description alone lacks the lifecycle context needed to select and invoke it reliably: it doesn't identify where session_id comes from, distinguish it from mitmweb_stop, or mention optional stop behavior. For a destructive stop operation with no annotations, this is a meaningful gap.

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 free-text description does not mention session_id, force, or timeout_seconds, and context reports 0% schema description coverage for parameters, so the description must compensate and does not. The only implied parameter is the session to stop, but mapping to the nested schema is left to the agent.

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 specifies a clear action ('Stop') and resource ('an active mitmproxy/mitmdump/mitmweb session'), and adds the effect 'release ports'. It is more specific than a bare name, but it doesn't explain how this relates to the sibling mitmweb_stop, which also appears to stop a mitmweb session.

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?

There is no statement of when to use this tool rather than mitmdump_start, mitmweb_stop, or other session lifecycle alternatives. It gives no conditions, prerequisites, or exclusions, so an agent must infer the intended usage from the name.

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