Browser MCP Server

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 states what the tool initiates ('tracking CSS and JavaScript code coverage') but doesn't explain what this tracking entails, how results are accessed, whether it affects browser performance, or what happens if called multiple times. The reference to external docs suggests missing 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 brief (one sentence) but not optimally structured. It front-loads the core action but includes a parenthetical reference to external documentation ('see browser_docs') that interrupts flow and suggests incompleteness. While concise, it could be more self-contained.

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?

For a tool with no annotations, no output schema, and behavioral complexity (starting performance tracking), the description is insufficient. It doesn't explain what 'tracking' produces, how to retrieve results, dependencies on other tools, or error conditions. The reference to external docs acknowledges gaps rather than filling them.

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 100%, so the schema fully documents the single parameter 'resetOnNavigation'. The description adds no parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter semantics.

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 ('Start tracking') and the resource ('CSS and JavaScript code coverage'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'browser_perf_stop_coverage' beyond the start/stop distinction, and the reference to 'browser_docs' suggests incomplete self-containment.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description references 'browser_docs' for more information, implying external documentation is needed, but within the description itself there's no context about prerequisites, sequencing with other tools, 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.