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. It discloses two behavioral traits: stopping monitoring and clearing logs. However, it doesn't mention important aspects like whether this is reversible, what permissions are needed, error conditions, or what happens to ongoing requests. The reference to 'browser_docs' suggests more information exists elsewhere but isn't provided here.

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 states the core action and effect. The parenthetical reference to 'browser_docs' adds helpful context without being verbose. However, it could be slightly more front-loaded by making the main action more prominent.

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 this is a mutation tool (stops monitoring and clears logs) with no annotations and no output schema, the description should provide more behavioral context. While it states what the tool does, it doesn't cover important aspects like side effects, error handling, or what confirmation/response to expect. The reference to documentation helps but doesn't substitute for a complete description.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't waste space discussing parameters. A baseline of 4 is appropriate for zero-parameter tools where the schema handles documentation completely.

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 the verb 'Stop' and resource 'network monitoring', and adds 'clear request log' as an additional effect. It distinguishes from sibling 'browser_net_start_monitoring' by being the opposite action. However, it doesn't fully differentiate from other monitoring-related tools like 'browser_sec_stop_csp_monitoring'.

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 implies usage context by referencing 'browser_docs' for more information, suggesting this should be used when network monitoring needs to be terminated. However, it doesn't explicitly state when to use this tool versus alternatives or what prerequisites exist (e.g., must monitoring be started first?).

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