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 emulates/throttles network conditions, implying a mutation that affects browser behavior, but doesn't disclose whether this is reversible, persistent across page navigation, requires specific permissions, or has side effects. The reference to external docs ('see browser_docs') shifts responsibility away from the description itself.

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 directly states the tool's purpose. However, the parenthetical '(see browser_docs)' is extraneous if the description should be self-contained, slightly reducing conciseness. Overall, it's appropriately sized with minimal waste.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after emulation (e.g., how to revert changes), error conditions, or typical return values. The reference to external docs suggests the description alone is insufficient for an agent to use the tool confidently.

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%, with clear parameter descriptions in the schema (e.g., 'Round-trip latency in ms', 'Download speed in bytes/second (-1 for unlimited)'). The tool description adds no parameter information beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without adding value.

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 tool 'Emulate network conditions (throttling)', which provides a clear verb ('Emulate') and resource ('network conditions'), but it's somewhat vague about scope and doesn't differentiate from sibling tools like browser_net_start_monitoring or browser_net_get_requests. The parenthetical '(throttling)' adds specificity but 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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an active browser page), typical use cases (e.g., testing slow network performance), or how it relates to sibling network tools like browser_net_start_monitoring. The agent must infer usage from context alone.

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