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 of behavioral disclosure. It effectively describes key behaviors: it exports content in one call, returns specific data types (HTML, title, meta tags, text), and includes size limits (50KB for HTML, 20KB for text). However, it doesn't mention potential side effects like performance impact or prerequisites (e.g., requires a loaded page).

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, with three sentences that each serve a distinct purpose: stating the action, detailing returns, and providing usage context. There is no wasted text, and key information is front-loaded for quick understanding.

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 moderate complexity (extracting multiple page elements), no annotations, and no output schema, the description does a good job covering what the tool does, when to use it, and what it returns. However, it lacks details on error handling or dependencies (e.g., browser context), leaving minor gaps in completeness.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description adds no parameter-specific information, which is appropriate since there are no parameters to document, maintaining clarity without redundancy.

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 ('Export', 'Returns') and resources ('rendered DOM content', 'rendered HTML, page title, meta tags, and visible text'). It distinguishes itself from sibling tools like 'get_page_html' by emphasizing comprehensive extraction in one call versus just HTML.

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 explicitly states when to use this tool: 'Saves writing ad-hoc evaluate_js scripts for common extraction needs.' This provides clear guidance on preferring this tool over alternatives like 'evaluate_js' for standard extraction tasks, helping the agent choose appropriately.

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