Start interception proxy

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

Covers key behaviors: starting proxy, CA generation/loading, and need for CA installation. No annotations provided, so description carries full burden. Misses side effects like idempotency or conflicts with existing proxy instances.

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?

Two sentences: first states purpose, second provides actionable instructions. No filler, front-loaded, every sentence adds value.

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?

Tool is simple with one optional parameter and no output schema. Description covers usage but does not mention return value (e.g., proxy URL or success status), leaving a minor 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?

Schema coverage is 100% for the sole parameter 'port' (default 8000). Description adds only usage context ('point at <host-ip>:<port>'), not additional semantics beyond schema.

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 tool starts the Mockttp HTTPS interception proxy and generates/loads a CA. It distinguishes from siblings like proxy_stop and adb_set_proxy.

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?

Describes when to use (to start proxy for capturing traffic) and provides instructions on pointing emulator and installing CA. Lacks explicit when-not-to-use or alternatives, but context is clear.

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