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 key behavioral traits: it can run in headless mode for debugging, emulates OS and locale, supports proxy and humanization features, and returns session state if the browser is already running. However, it doesn't mention potential side effects like resource consumption or error conditions.

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 well-structured with clear sections (Args, Returns) and front-loaded purpose. Each sentence adds value, but it could be slightly more concise by integrating the purpose statement with the parameter explanations to reduce redundancy.

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 complexity (8 parameters, no annotations, no output schema), the description is largely complete. It explains parameters thoroughly and outlines return values. However, it could improve by detailing error handling or performance implications, which are relevant for a browser-launching tool.

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 description coverage is 0%, so the description must compensate. It provides detailed semantics for all 8 parameters, explaining defaults (e.g., headless default False for debugging), options (e.g., os_type values), and effects (e.g., locale affects Accept-Language headers). This adds significant value beyond the bare 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 starts with a specific verb ('Launch') and resource ('Camoufox anti-detection browser'), clearly stating what the tool does. It distinguishes itself from siblings like 'close_browser' or 'get_session_info' by focusing on initialization rather than interaction or retrieval.

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 for launching a browser with anti-detection features, but lacks explicit guidance on when to use it versus alternatives (e.g., no mention of prerequisites or scenarios where it's preferred over other browser-related tools). It mentions 'If browser is already running' but doesn't specify how to handle that case versus using 'get_session_info'.

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