camoufox-reverse-mcp

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

No annotations are provided, so the description carries full burden. It states the tool deletes cookies and returns a status/count, but lacks critical behavioral details: whether deletion is permanent, requires specific permissions, affects browser state, has side effects (e.g., logging out users), or handles errors. For a destructive operation with zero annotation coverage, this is insufficient.

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 concise: a clear purpose statement followed by Args and Returns sections. Each sentence adds value—no fluff. It efficiently communicates core functionality in minimal space.

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 2 parameters with 0% schema coverage and no output schema, the description partially compensates by explaining parameters and return format. However, as a destructive tool with no annotations, it should include more behavioral context (e.g., safety warnings, typical use cases). It's adequate but leaves gaps for an agent to operate safely.

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. It explains both parameters: 'name' deletes a specific cookie, and 'domain' deletes all cookies for a domain. This clarifies their roles beyond schema titles. However, it doesn't detail format (e.g., domain syntax) or interaction (e.g., using both parameters together).

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: 'Delete cookies by name and/or domain.' It specifies the verb ('Delete') and resource ('cookies') with optional filters. However, it doesn't explicitly distinguish from sibling tools like 'get_cookies' or 'set_cookies' beyond the obvious action difference.

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., browser must be launched), compare with 'set_cookies' for modification, or specify scenarios like clearing session data. The agent must infer usage from context alone.

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