camoufox-reverse-mcp

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

With no annotations provided, the description carries the full burden. It discloses the return value format ('dict with status and total number of captured requests'), which is helpful behavioral information. However, it doesn't mention potential side effects (e.g., whether stopping is reversible, if data is preserved), error conditions, or dependencies on other tools like 'start_network_capture'. The disclosure is basic but adds value beyond the minimal purpose statement.

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 extremely concise with just two sentences: one stating the action and one describing the return value. Every sentence earns its place by providing essential information without any fluff or redundancy. It's front-loaded with the core purpose.

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 tool has 0 parameters, no annotations, and no output schema, the description provides the minimum viable information: purpose and return format. However, for a tool that presumably interacts with network capture state (implied by sibling 'start_network_capture'), it lacks details about prerequisites, error handling, or what happens to captured data after stopping. The completeness is adequate but has clear gaps in behavioral 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 tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to explain any parameters, which is appropriate. It gets a baseline 4 since no parameter information is required, and it doesn't incorrectly mention any parameters.

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 action ('Stop capturing') and resource ('network requests'), making the purpose unambiguous. It distinguishes from sibling 'start_network_capture' by indicating it's the complementary stop operation, though it doesn't explicitly differentiate from other tools like 'stop_intercept' which might have overlapping network-related functions.

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 usage context by referencing 'capturing network requests', suggesting it should be used after starting a capture. However, it doesn't explicitly state when to use this tool versus alternatives like 'stop_intercept' or provide clear prerequisites (e.g., must have an active capture). The guidance is implied rather than explicit.

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