Browser MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks critical details: it doesn't specify if this tool requires the input field to be focused first, whether it simulates real typing or sets text directly, potential side effects (e.g., triggering events), or error handling. The reference to 'browser_docs' hints at external documentation but doesn't add behavioral context within 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 brief and to the point, using a single sentence to convey the core action. However, the parenthetical reference to 'browser_docs' adds minor clutter without enhancing clarity in the description itself. It's front-loaded with the main purpose but 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?

Given the complexity of a browser automation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error conditions, and interaction with sibling tools. The reference to external docs suggests incompleteness, making it inadequate for standalone use by an AI agent in this context.

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 input schema has 100% description coverage, with clear documentation for both parameters ('selector' and 'text'). The description adds no additional semantic meaning beyond what the schema provides, such as examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't 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 states the action ('Type text') and target ('into an input field'), which provides a basic purpose. However, it's vague about what distinguishes this from similar tools like browser_press_key or browser_focus, and the reference to 'browser_docs' suggests incomplete self-containment. It doesn't clearly differentiate from siblings beyond the general action.

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 offers no explicit guidance on when to use this tool versus alternatives. While it references 'browser_docs' for more information, this is not a direct usage guideline. There's no mention of prerequisites, context, or comparisons to sibling tools like browser_press_key for keyboard input or browser_focus for field activation.

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