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. It discloses the tool reads data (implied non-destructive) and mentions default values and max limits for parameters, which is useful behavioral context. However, it doesn't cover potential errors (e.g., invalid request_id), performance implications, or authentication needs, leaving gaps for a mutation-like tool.

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 with the core purpose, followed by clear sections for Args and Returns. Every sentence earns its place: the first explains the tool's role, and the subsequent lines efficiently document parameters and return values without redundancy.

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 no annotations and no output schema, the description does a good job covering the tool's purpose, parameters, and return structure. It explains the pagination context and parameter defaults. However, for a tool that reads potentially sensitive data (response bodies), it lacks details on permissions or error handling, which could be important for 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?

Schema description coverage is 0%, so the description must compensate fully. It provides detailed semantics for all three parameters: request_id's source (list_network_requests), offset's meaning (character offset to start reading), and length's details (default, max). This adds significant value beyond the bare schema, effectively documenting parameter purposes and constraints.

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 verb 'Read' and resource 'a slice of a captured response body', specifying it's for 'paginated viewing of large responses'. This distinguishes it from siblings like get_network_request or search_response_body by focusing on paginated access to response body content rather than full retrieval or searching.

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: it's for 'paginated viewing of large responses', implying use when response bodies are too large to handle at once. It references list_network_requests as the source for request_id, establishing a prerequisite. However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among siblings.

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