camoufox-reverse-mcp

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a mutation tool (makes method non-overridable), explains the effect on page scripts (attempts to reassign will silently fail or throw in strict mode), and mentions the purpose in a security/hooking context. It doesn't cover error conditions or side effects beyond the core behavior.

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?

Appropriately sized and front-loaded: the first sentence states the core purpose, followed by behavioral details, usage guidance, and parameter explanations. Every sentence adds value with no wasted words, and the structure flows logically from what to why to how.

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 (mutation with security implications), no annotations, and no output schema, the description is mostly complete: it covers purpose, behavior, usage, and parameters. However, it lacks details on error cases (e.g., invalid class/method) and the exact structure of the return dict, leaving some gaps for a mutation 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 provides clear meaning for both parameters: 'class_name' is explained as 'The class/constructor name' with examples like 'XMLHttpRequest', and 'method_name' as 'The method name on the prototype' with examples like 'open'. This adds essential context 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 ('Make a prototype method non-overridable by page scripts') and the resource ('prototype method'), distinguishing it from siblings like hook_function or trace_function. It explains the technical effect of preventing reassignment by page JavaScript.

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?

Explicitly provides when to use ('Use after installing hooks to prevent the target site from restoring original methods'), offering clear context for application. It distinguishes this as a protective measure following hook installation, unlike general hooking or tracing tools.

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