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 by disclosing key behavioral traits: the search is case-insensitive, returns matches with context around matches, includes a default max_results value, and mentions the prerequisite. It doesn't cover potential limitations like performance impacts or error conditions, 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?

Perfectly structured with purpose statement, prerequisite, parameter explanations, and return format - all in minimal sentences. Every sentence earns its place with essential information. The Args/Returns formatting enhances readability without verbosity.

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, 0% schema coverage, and no output schema, the description provides excellent coverage of purpose, prerequisites, parameters, and return format. The only minor gap is not explicitly mentioning what happens when no matches are found or potential error conditions, but otherwise very 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?

Schema description coverage is 0%, so the description must fully compensate - and it does. Each parameter (keyword, url_filter, max_results) is clearly explained with semantics beyond just naming: keyword is a case-insensitive substring search, url_filter narrows scope, max_results has a default of 20. This adds significant value 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 ('Search for a keyword across all captured response bodies') and distinguishes it from siblings by focusing on response body content rather than code, network requests, or other search targets. It uses precise terminology that differentiates its domain.

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?

Explicitly states a prerequisite ('Requires start_network_capture(capture_body=True) to have been called first'), which provides clear when-to-use guidance. This is essential context that distinguishes it from tools that might work independently or have different prerequisites.

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