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 and does well by disclosing key behavioral traits: it captures specific data (arguments, call stack, etc.), stores it in 'window.__mcp_breakpoints', and mentions persistence across page navigation. However, it lacks details on permissions, rate limits, 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: the first sentence states the purpose, followed by details on data capture and storage, then a structured 'Args' and 'Returns' section. Every sentence adds value without waste.

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?

For a tool with no annotations, no output schema, and 3 parameters, the description is quite complete—covering purpose, usage, parameters, and return value. It could improve by mentioning side effects or linking more explicitly to sibling tools, but it provides sufficient context for effective use.

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?

Given 0% schema description coverage, the description fully compensates by explaining all three parameters: 'target_function' with examples, 'script_url_pattern' as optional for limiting scripts, and 'persistent' for survival across navigation. 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 ('Set a pseudo-breakpoint on a function via JS hooking') and the resource ('function'), distinguishing it from siblings like 'trace_function' or 'hook_function' by specifying it captures comprehensive data (arguments, call stack, etc.) and stores it for retrieval with 'get_breakpoint_data'.

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 (to capture function call data via hooking) and implicitly suggests an alternative ('get_breakpoint_data' for retrieval), but it does not explicitly state when not to use it or compare it to similar siblings like 'trace_function'.

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