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 search behavior (case-sensitive substring match), result format (matching lines with 2 lines of surrounding context), and truncation behavior (total_matches shows real total when truncated). It doesn't mention performance implications or rate limits, but covers core behavioral aspects adequately.

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?

Well-structured with purpose first, then behavioral details, followed by parameter explanations and return format. Every sentence earns its place with no wasted words. The information is front-loaded with the core functionality stated immediately.

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 search tool with no annotations and no output schema, the description does very well: explains purpose, behavior, parameters, and return format. It could mention performance considerations for searching many scripts, but covers the essential context needed to use the tool effectively.

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 fully. It provides excellent parameter semantics: explains 'keyword' as 'case-sensitive substring match' and 'max_results' with default value (50) and maximum (200). 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 specific action ('Search for a keyword'), target resource ('across all loaded JavaScript sources in the page'), and scope ('fetches each script's source'). It distinguishes from siblings like 'search_code_in_script' by specifying it searches across ALL scripts rather than a specific one.

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 clear context about what the tool does (searching across all JavaScript sources), but doesn't explicitly state when to use this versus alternatives like 'search_code_in_script' or 'search_response_body'. The context is clear but lacks explicit sibling differentiation.

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