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 starts a capture process, includes details on what data is captured (URL, method, headers, etc.), mentions memory usage implications for 'capture_body', and references a related tool for viewing results. This covers most critical aspects, though it lacks details on rate limits or error handling.

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 front-loaded, starting with the core purpose, followed by details on captured data and usage guidance, and ending with parameter explanations. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 (starting a network capture with configurable parameters), no annotations, and no output schema, the description is largely complete. It covers purpose, usage, parameters, and behavioral context. However, it lacks explicit return value details (only mentions a 'dict with status and pattern'), which could be more detailed for a tool with no output schema.

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 significant meaning beyond the input schema, which has 0% coverage. It explains that 'url_pattern' is a glob pattern with a default to capture all URLs, and 'capture_body' affects memory usage and allows inspecting response data. This compensates fully for the schema's lack of descriptions, providing clear semantics for both parameters.

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 a specific verb ('Start capturing') and resource ('network requests matching the given URL pattern'). It distinguishes from sibling tools by mentioning 'list_network_requests' as a separate tool for viewing captures, making its role in the capture workflow explicit.

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 for usage by explaining that captured data can be viewed with 'list_network_requests'. However, it does not explicitly state when not to use this tool or mention alternatives like 'stop_network_capture' (a sibling tool) for comparison, leaving some guidance gaps.

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