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 key traits: the tool injects hooks with Object.defineProperty protection for security, defaults to persistence across navigations, and specifies what each preset does (e.g., logging requests or bypassing debuggers). However, it does not cover potential side effects like performance impacts or error handling, leaving some gaps.

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 with the core purpose, followed by a bulleted list of presets and clear parameter explanations. Every sentence adds value—no fluff—making it efficient and easy to parse for an AI agent.

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 (2 parameters, no output schema, no annotations), the description is largely complete: it covers purpose, usage, parameters, and behavior. However, it lacks details on return values (only mentions a dict with status and preset name without specifics) and does not address potential errors or limitations, leaving minor gaps in full 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%, so the description must compensate fully. It does so by clearly explaining both parameters: 'preset' is detailed with an enumerated list of options and their functions, and 'persistent' is defined with its default behavior and effect on hook survival. This adds 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 ('inject a pre-built hook template') and resources ('common reverse engineering tasks'), distinguishing it from siblings like 'hook_function' or 'bypass_debugger_trap' by focusing on preset templates rather than custom hooks or single bypasses. It explicitly lists available presets, making the scope concrete and actionable.

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—for injecting predefined hooks in reverse engineering—and implies alternatives by listing specific presets (e.g., 'xhr' vs. 'fetch'), but it does not explicitly state when not to use it or compare it to sibling tools like 'hook_function' for custom hooks. This gives good guidance but lacks explicit exclusions.

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