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 opens a browser to a specific type of site (detection sites), captures a screenshot, and returns a dict with base64 data and issues. However, it doesn't mention potential side effects (e.g., browser state changes), performance characteristics, or error handling.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The Args and Returns sections are well-structured, though the second sentence could be integrated more tightly. Every sentence adds value, with minimal 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 tool's moderate complexity (navigation and screenshot capture), no annotations, no output schema, and 1 parameter with 0% schema coverage, the description is mostly complete. It covers purpose, usage, parameters, and return format, but lacks details on error cases or the structure of 'detected issues' in the return dict.

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 input schema has 0% description coverage for its single parameter 'url', but the description compensates fully. It explains the parameter's purpose ('Detection site URL'), provides a default value, and lists three common choices with examples, adding significant meaning 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 clearly states the tool's purpose with specific verbs ('Navigate', 'take a screenshot', 'Opens', 'captures') and resources ('bot detection site', 'fingerprint/bot detection site', 'screenshot'). It distinguishes from sibling tools like 'take_screenshot' by specifying it's for detection verification with a default site, not general screenshot capture.

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 provides clear context for when to use this tool ('to verify anti-detection', 'for visual inspection of detection results'), but doesn't explicitly state when not to use it or name alternatives among siblings. It implies usage in anti-detection testing scenarios without exclusions.

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