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. While it mentions the tool calls CDP commands, it doesn't describe what happens on failure, whether it requires specific browser states, what permissions are needed, or what the response format looks like. For a tool that interacts with browser debugging protocols, this leaves significant behavioral unknowns.

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 immediately communicates the core functionality. Every word earns its place, with no redundant information or unnecessary elaboration. It's appropriately sized for a tool with this level of complexity.

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 complexity (CDP interaction with 4 parameters), complete lack of annotations, and 0% schema coverage, the description is insufficiently complete. While an output schema exists (which helps with return values), the description doesn't provide enough context about when to use this tool, parameter meanings, or behavioral characteristics for safe and effective use.

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?

With 0% schema description coverage and 4 parameters (1 required), the description provides no parameter information beyond what's implied by the tool name. It doesn't explain what 'method' should contain (specific CDP method names), how 'params_json' should be formatted, what 'session_id' refers to, or when to use 'tab_id'. The description fails to compensate for the complete lack of schema documentation.

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 action ('Call a single Chrome DevTools Protocol command') and target ('on the current or specified tab'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like 'cdp_batch' (which handles multiple commands) or 'execute_js' (which is JavaScript-specific rather than general CDP).

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 minimal guidance - it mentions 'current or specified tab' which gives some context about tab targeting, but offers no explicit when-to-use advice, no comparison to alternatives like 'cdp_batch' for multiple commands, and no prerequisites or limitations. The agent must infer usage from the tool name and description alone.

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