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: it explains the tool's behavior ('runs automatically before any page JavaScript'), timing implications ('ensuring interception is in place'), and persistence effects ('survives page navigation, new tabs, and reload automatically'). It doesn't cover error handling or security constraints, but provides substantial operational context.

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 with a clear purpose statement, usage context, parameter explanations, and return information. Every sentence earns its place, though it could be slightly more front-loaded by moving the return statement earlier. It efficiently covers complex functionality without unnecessary verbiage.

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 (script injection with persistence options), no annotations, 0% schema coverage, and no output schema, the description does remarkably well. It explains the tool's behavior, parameters, and returns, though it could benefit from mentioning error cases or compatibility constraints. For a mutation tool with no structured support, this is nearly complete.

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?

With 0% schema description coverage and 4 parameters, the description fully compensates by explaining each parameter's purpose and relationships: 'script' vs 'path' as alternatives, 'persistent' for context-level injection with survival benefits, and 'name' for later removal of persistent scripts. This adds 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 tool's purpose with specific verbs ('inject a script that runs automatically') and resources ('before any page JavaScript on every navigation'). It distinguishes itself from siblings by focusing on script injection for hook installation, unlike tools like 'evaluate_js' or 'inject_hook_preset' which have different scopes.

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 usage guidance: it states this is 'the core method for installing hooks' and explains when to use persistent mode ('Recommended for hooks that must always be present'). It differentiates from alternatives by specifying its unique timing ('before any page JavaScript loads'), helping the agent choose this over other injection or hook-related tools.

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