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 creates a new context, loads state (cookies, localStorage, sessionStorage), and switches to it. However, it lacks details on permissions, side effects (e.g., if existing contexts are affected), or error handling. It adds value but is not comprehensive for a mutation tool.

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: the first sentence states the core purpose, followed by details on behavior, args, and returns. Each sentence earns its place with no wasted words, and the structure (purpose, behavior, parameters, returns) is logical and efficient.

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 no annotations, 0% schema coverage, and no output schema, the description does well: it explains the tool's purpose, behavior, parameter, and return value. However, for a mutation tool that creates a new context, it could mention potential impacts (e.g., context management) or error cases, leaving minor gaps in completeness.

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 fully. It explicitly documents the single parameter 'state_path' with its purpose ('Path to the state JSON file') and source ('exported by export_state'), adding crucial meaning beyond the schema's basic string type. This fully compensates for the lack of schema descriptions.

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 specific action ('import browser state from a JSON file by creating a new context') and resource ('browser state'), distinguishing it from siblings like 'export_state' (which exports) and 'launch_browser' (which creates a fresh context). The verb 'import' and resource 'browser state' are precise and unambiguous.

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 usage: 'Creates a new browser context with the saved state... and switches to it.' It implies this is for restoring saved state, but does not explicitly state when not to use it (e.g., vs. 'launch_browser' for a fresh context) or name alternatives, though the sibling 'export_state' is mentioned as the source. This is clear context without exclusions.

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