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 describes the core functionality (extraction with dot-notation, array indexing, wildcard support) and return format, but lacks details on error handling, performance characteristics, or dependencies on other tools (e.g., requiring a captured response first). It adds meaningful context beyond basic parameters.

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 appropriately sized, with a clear purpose statement followed by parameter explanations and return information. Every sentence adds value without redundancy, and it uses bullet-like formatting for readability while maintaining conciseness.

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 moderate complexity (2 parameters, no output schema, no annotations), the description is largely complete. It covers purpose, usage, parameters, and returns, but could benefit from mentioning prerequisites (e.g., needing a captured response via another tool) or error scenarios. The lack of output schema is mitigated by describing the return format.

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 semantic value beyond the input schema, which has 0% description coverage. It explains both parameters thoroughly: 'request_id' as the identifier for the captured response, and 'json_path' with syntax examples (dot-notation, array indexing, wildcards) and use cases. This fully compensates for the schema's lack of descriptions.

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 verbs ('extract a value') and resources ('captured JSON response body'), using technical terminology ('dot-notation path'). It distinguishes itself from siblings by focusing on JSON path extraction rather than broader search or analysis functions like 'search_response_body' or 'search_code'.

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 when to use this tool (extracting values from JSON responses) and includes usage examples, but does not explicitly state when not to use it or name specific alternatives among sibling tools. The context is sufficient for general guidance without explicit exclusions.

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