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 mentions 'clear violations' which implies a destructive action, but doesn't clarify if this is reversible, what permissions are needed, or what the expected outcome looks like. The description is minimal and lacks behavioral context beyond the basic operation.

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 extremely concise (one sentence) and front-loaded with the core action. However, the parenthetical reference to 'browser_docs' feels like an afterthought rather than integrated guidance, slightly reducing effectiveness.

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 that performs a potentially destructive action (clearing violations) with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after stopping monitoring, what 'clear violations' means operationally, or what the agent should expect as a result. The reference to external documentation doesn't compensate for missing contextual information.

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 input requirements. The description appropriately doesn't discuss parameters since none exist, which is correct for this case.

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 states the action ('Stop CSP monitoring and clear violations') which is a specific verb+resource combination, but it's somewhat vague about what CSP monitoring entails. It doesn't clearly differentiate from sibling tools like 'browser_sec_get_csp_violations' or 'browser_sec_start_csp_monitoring' beyond the obvious stop vs start distinction.

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. There's no mention of prerequisites (like needing to have started monitoring first), nor does it indicate what happens if monitoring isn't active. The reference to 'browser_docs' suggests documentation exists elsewhere but isn't integrated into the description.

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