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 'Read' but doesn't clarify what 'content and metadata' includes, whether it's a read-only operation, potential side effects, or error conditions. This leaves significant gaps in understanding how the tool behaves.

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, which is efficient. However, the parenthetical reference to 'browser_docs' adds a dependency without explaining its relevance, slightly reducing clarity. It's front-loaded with the core action 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 browser interactions and the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'content and metadata' entails, the format of the return value, or how it integrates with other tools, making it incomplete for effective use.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and since there are none, it meets the baseline for this dimension without requiring additional details.

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 verb 'Read' and the resource 'content and metadata of the current page', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'browser_get_dom' or 'browser_get_text', which might also retrieve page content, so it falls short of a perfect score.

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 minimal guidance by referencing 'browser_docs' for more information, but it lacks explicit instructions on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing an active page) or comparisons to siblings, leaving usage unclear.

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