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 of behavioral disclosure. It effectively describes the tool's behavior: it executes JavaScript in the page context, returns a result with its type, and handles promises via the await_promise parameter. However, it doesn't mention potential risks (e.g., side effects, security implications) or performance considerations, which would be valuable for a powerful tool like this.

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 and front-loaded, starting with the core purpose, followed by usage context, examples, and parameter details. Every sentence earns its place by providing necessary information without redundancy, making it efficient and easy to parse.

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 complexity (executing arbitrary JavaScript) and lack of annotations and output schema, the description is largely complete. It covers purpose, usage, parameters, and return format. However, it could improve by mentioning error handling or limitations (e.g., execution context constraints), which would be helpful for such a powerful 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 fully. It does so by clearly explaining both parameters: 'expression' as the 'JavaScript expression to evaluate' with examples, and 'await_promise' as controlling whether to 'awaits Promise results' with its default value. This adds essential 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 ('Execute an arbitrary JavaScript expression'), the resource ('in the page context'), and the outcome ('return the result'). It explicitly distinguishes this tool from siblings by calling it 'the most fundamental and powerful tool for reverse engineering,' which helps differentiate it from more specialized tools like evaluate_js_handle or hook_function.

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 explicit guidance on when to use this tool ('for reverse engineering' and 'to inspect variables, call functions, check prototypes, etc.') and includes concrete examples that illustrate common use cases. It implicitly suggests alternatives by positioning it as a general-purpose tool, though it doesn't explicitly name sibling tools for comparison.

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