Mitm Execute Command

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It hints via examples that commands can clear views or kill flows, but it does not state destructive potential, allowlist failure behavior, session requirements, or output/error behavior.

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 with a direct verb, scope, and two illustrative examples. Every word earns its place and there is no filler.

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 generic command executor with nested parameters and no annotations, this is under-specified: an agent still needs to know where session_id comes from, how arguments bind, what happens for non-allowlisted commands, and what success/failure looks like.

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?

With schema description coverage reported at 0% and no annotations, the description must compensate, but it only gives examples for 'command' and calls the session 'active'. It does not explain how to obtain or format session_id, what arguments mean, or how arguments map to a command.

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 names a clear verb ('execute'), a resource ('allowlisted command'), and a context ('active mitmweb session'), with concrete examples ('view.clear', 'flow.kill'). It does not explicitly contrast with sibling tools, so it stops short of full sibling differentiation.

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?

It implies a prerequisite (an active mitmweb session) and an allowlist of commands, but gives no guidance on when to choose this tool over the many specialized mitm_* siblings. There is no when-not-to-use or alternative recommendation.

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