agent-browser-mcp

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 effectively communicates key behaviors: it's a read operation ('Read'), it preserves authentication state, it simplifies HTML/text, and it operates on the 'current page' context. However, it doesn't mention potential limitations like rate limits, error conditions, or what 'simplified' specifically entails.

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, well-constructed sentence that efficiently communicates the core functionality. Every word earns its place: 'Read' establishes the action, 'current page' specifies the target, 'simplified HTML/text' describes the output format, and 'preserving login state from the real browser' adds crucial behavioral context.

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 with 6 parameters (0% schema coverage) and no annotations, the description does an adequate job explaining the core purpose and key behavior. However, it completely ignores parameter semantics, and while an output schema exists, the description doesn't hint at return format or structure. The presence of many sibling tools suggests this operates in a browser automation context that could use more explicit positioning.

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?

With 0% schema description coverage for 6 parameters, the description provides no information about any parameters. It doesn't mention session_id for session management, text_only for format control, cutlist for content filtering, maxchars for output limits, instruction for processing guidance, or extra_js for JavaScript injection. The description fails to compensate for the complete lack of schema documentation.

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'), resource ('current page'), and key behavioral characteristics ('simplified HTML/text', 'preserving login state from the real browser'). It distinguishes itself from screenshot siblings like capture_page_screenshot by focusing on content extraction rather than visual capture.

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 (when you need to extract page content while maintaining authentication state), but doesn't explicitly state when to use this versus alternatives like execute_js for JavaScript execution or get_cookies for cookie management. No specific exclusions or prerequisites are mentioned.

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