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 for behavioral disclosure. It helpfully mentions performance considerations ('Set False for large responses' and 'Set False to save tokens'), which adds practical context beyond basic functionality. However, it doesn't address other important behavioral aspects like error conditions, authentication requirements, rate limits, or whether this is a read-only operation (though 'Get' implies it likely is).

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 perfectly structured and concise: a clear purpose statement followed by organized sections for Args and Returns. Every sentence earns its place by providing essential information without redundancy. The formatting with clear section headers makes it easily scannable.

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 3 parameters with 0% schema coverage and no output schema, the description does an excellent job explaining parameters and return format. However, for a tool in a complex browser automation/testing context with many sibling tools, it could benefit from more explicit guidance about when this tool fits into typical workflows versus alternatives. The lack of annotations means the description carries extra weight, which it handles well but not perfectly.

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. It provides excellent parameter semantics: it explains what 'request_id' is and where to get it, clarifies the purpose and default values for 'include_body' and 'include_headers', and gives practical guidance about when to set them to False. This adds substantial 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 tool's purpose with specific verb ('Get full details') and resource ('specific captured network request'), and distinguishes it from sibling tools by referencing 'list_network_requests' as the source for request IDs. It explicitly indicates this is for retrieving detailed information about a single request rather than listing or capturing requests.

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 by specifying that request IDs come from 'list_network_requests', establishing a usage dependency. However, it doesn't explicitly state when NOT to use this tool or mention alternatives among the many sibling tools (like 'get_response_body_page' or 'search_response_body'), which would be helpful given the extensive toolset.

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