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. While it mentions reading fingerprint data and the verification purpose, it doesn't disclose important traits like whether this operation is safe/read-only, if it requires specific browser states, potential rate limits, or side effects. The description provides basic intent but lacks operational details.

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 with clear sections: purpose statement, operational details, and return value specification. It's appropriately sized at 4 sentences with no redundant information. Minor improvement could be made by front-loading the return details more prominently.

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 (fingerprint data collection), no annotations, and no output schema, the description provides adequate coverage of what data is collected and the verification purpose. However, it lacks details on the return structure format, potential errors, or browser state requirements that would be helpful for an agent.

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 tool has 0 parameters with 100% schema description coverage (empty schema). The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and return values. This meets the baseline expectation for parameterless tools.

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 ('Get') and resource ('current browser fingerprint information'), with explicit details on what data is collected (navigator, screen, WebGL, canvas). It distinguishes itself from sibling tools like 'get_cookies' or 'get_session_info' by focusing specifically on browser fingerprinting data.

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 implies usage context ('to verify what fingerprint the anti-detection engine is presenting'), suggesting this tool is for fingerprint verification in anti-detection scenarios. However, it doesn't explicitly state when to use this versus alternatives like 'compare_env' or 'check_detection', nor does it provide exclusion criteria.

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