Browser Instrumentation MCP Server

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 states what the tool does but lacks critical details: it doesn't specify if this is a read-only operation, whether it requires specific permissions, how it captures logs (e.g., real-time vs. buffered), or any rate limits. The mention of 'captured' hints at stored data but doesn't clarify behavior beyond the basic action.

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 front-loaded, with the core purpose in the first sentence and additional details in a clear 'Args'/'Returns' format. Every sentence earns its place by providing essential information without redundancy, making it efficient and easy to parse.

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 (single parameter, no annotations, but with an output schema), the description is partially complete. It explains the purpose and return format, but lacks usage guidelines, behavioral context, and full parameter semantics. The output schema mitigates the need to detail return values, but other gaps remain, making it adequate but with clear room for improvement.

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 explicitly documents the 'session' parameter, adding meaning beyond the input schema (which has 0% description coverage). However, it only names the parameter without explaining its semantics (e.g., what constitutes a valid session name, how to obtain it from sibling tools like 'browser_session_list'). With one parameter and low schema coverage, this provides some compensation but leaves gaps.

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 a specific verb ('Get') and resource ('captured console log messages from the page'), making it immediately understandable. However, it doesn't explicitly distinguish this from sibling tools like 'browser_inspect_dom' or 'browser_inspect_events', which also inspect page elements but target different resources.

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 prerequisites (e.g., requiring an active browser session), exclusions, or how it differs from other inspection tools like 'browser_inspect_text' or 'browser_inspect_network', leaving the agent to infer usage context from the tool name alone.

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