Browser MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states the tool starts monitoring with detailed timing, which implies a stateful, ongoing operation, but fails to disclose critical behavioral traits: whether it requires an active browser session, if it runs in the background, how to access monitored data (likely via 'browser_net_get_requests'), or any side effects like performance impact. The mention of 'detailed timing' adds some value but is insufficient for a mutation tool.

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 vague reference to 'browser_docs' that adds little immediate value. While concise, it could be more informative by integrating key usage details directly, making it somewhat under-specified rather than efficiently packed.

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 complexity of starting a monitoring operation with no annotations and no output schema, the description is incomplete. It lacks essential context: how the monitoring works, what data is produced, how to stop it (via 'browser_net_stop_monitoring'), or dependencies on other tools. For a state-initiating tool in a rich sibling set, this leaves significant gaps for an AI agent to operate effectively.

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 schema description coverage is 100%, with the 'patterns' parameter fully documented in the schema as 'URL patterns to monitor (default: all)'. The description adds no additional parameter information beyond what the schema provides, such as syntax examples or timing details. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 monitoring network requests') and the resource ('network requests'), specifying it includes 'detailed timing'. It distinguishes itself from siblings like 'browser_net_get_requests' by indicating it initiates monitoring rather than retrieving data. However, it lacks explicit differentiation from 'browser_net_stop_monitoring' beyond the verb, and the reference to 'browser_docs' is vague.

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 does not mention prerequisites (e.g., needing an active browser page), exclusions, or comparisons to siblings like 'browser_net_get_requests' or 'browser_net_stop_monitoring'. The reference to 'browser_docs' implies external documentation but does not offer direct usage context.

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