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: the tool reloads the page (a disruptive action) and optionally preserves persistent hooks. However, it misses details like whether the reload is immediate, if user data is lost, 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 action in the first sentence. The Args and Returns sections are structured but slightly verbose; every sentence earns its place by clarifying parameter behavior and output.

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, no output schema, and a single parameter with 0% schema coverage, the description is moderately complete. It covers the tool's purpose and parameter semantics well but lacks details on the return value (e.g., what 'status' includes) and broader 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?

Schema description coverage is 0%, but the description fully compensates by explaining the 'keep_persistent' parameter's semantics (preserving context-level hooks vs. removing all hooks) and its boolean logic, adding crucial 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 specific action ('Remove all injected hooks') and mechanism ('by reloading the page'), distinguishing it from siblings like 'hook_function' or 'inject_hook_preset'. It precisely defines what the tool does without being tautological.

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 (e.g., after hooks are injected) but does not explicitly state when to use this tool versus alternatives like 'reload' or 'close_browser'. It provides clear guidance on the 'keep_persistent' parameter but lacks sibling differentiation.

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