camoufox-reverse-mcp

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

No annotations are provided, so the description carries the full burden. It states the action ('click') but lacks behavioral details such as whether it waits for the element to be clickable, handles errors if the selector fails, requires specific page states, or has side effects like page navigation. This leaves significant gaps for a mutation tool.

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 front-loaded with the core action, followed by structured sections for arguments and returns. Every sentence earns its place: the first states the purpose, and the subsequent lines efficiently document inputs and outputs without redundancy.

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 (a mutation action with potential side effects), no annotations, no output schema, and only basic parameter documentation, the description is incomplete. It doesn't cover error handling, behavioral nuances, or output details beyond a vague 'dict with status,' leaving the agent with insufficient context for reliable 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?

The description adds meaningful context beyond the schema, which has 0% coverage. It explains that 'selector' is a 'CSS selector of the element to click,' clarifying the parameter's purpose and format. Since there's only one parameter, this adequately compensates for the schema's lack of descriptions.

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 action ('click on a page element') and resource ('page element'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'type_text' or 'navigate' which also interact with page elements, though the specific action is distinct.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a page loaded), exclusions (e.g., not for non-interactive elements), or comparisons with similar tools like 'type_text' for text input or 'navigate' for navigation actions.

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