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 tool's behavior by stating it returns a dict with the accessibility tree snapshot and its semantic content, but lacks details on potential side effects, performance implications, or error conditions. It adds some value but does not fully cover behavioral traits like rate limits or dependencies.

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 front-loaded with the core purpose in the first sentence, followed by efficiency benefits and return details, with every sentence earning its place. It is appropriately sized, avoiding redundancy and waste, making it easy to parse quickly.

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 low complexity (0 parameters, no output schema, no annotations), the description is mostly complete, covering purpose, usage context, and return format. However, it could benefit from more behavioral details like error handling or prerequisites, slightly reducing completeness for a tool with no structured safety hints.

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, so the schema already fully documents the inputs. The description does not need to add parameter information, and it appropriately focuses on the tool's purpose and output. Baseline is 4 for zero parameters, as no compensation is needed.

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 ('Get the accessibility tree') and resources ('current page'), distinguishing it from sibling tools like 'take_screenshot' by emphasizing its structured text representation and token efficiency for AI analysis. It explicitly contrasts with screenshots, making its unique function clear.

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 on when to use this tool ('More token-efficient than screenshots for AI analysis'), implying it's preferred for semantic structure analysis over visual capture. However, it does not explicitly state when not to use it or name alternatives beyond the implied comparison with 'take_screenshot', missing explicit exclusions.

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