agent-browser-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 mentions passing 'the full JSON command object as text' which implies a specific input format, but doesn't describe what happens during execution (e.g., whether it's synchronous/asynchronous, error handling, performance characteristics, or what the CDP bridge actually does). For a tool that appears to execute browser commands, this is a significant gap in behavioral context.

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 a single, efficient sentence that gets straight to the point. There's no wasted language or unnecessary elaboration. However, it could be slightly more structured by separating the core purpose from parameter guidance.

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 that there's an output schema (which means return values are documented elsewhere), the description doesn't need to explain return values. However, for a tool with 2 parameters (one completely undocumented), no annotations, and 0% schema description coverage, the description should do more to explain what CDP bridge is, what batch commands are available, and how this differs from 'cdp_command'. The current description is minimally adequate but leaves important gaps.

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. It explains that 'batch_json' should contain 'the full JSON command object as text', which adds meaningful context about the parameter's content and format. However, it doesn't explain what constitutes a valid JSON command object or provide examples. The 'session_id' parameter is not mentioned at all, leaving it completely undocumented.

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 states the tool 'Run a CDP bridge batch command', which provides a verb ('Run') and resource ('CDP bridge batch command'), but it's somewhat vague about what CDP bridge is and what types of batch commands are supported. It doesn't clearly differentiate from sibling tools like 'cdp_command', which appears to be a similar single-command tool.

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 no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'cdp_batch' over 'cdp_command' or other browser automation tools like 'execute_js' or 'scan_page'. There's no context about prerequisites or typical use cases.

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