MCP Browser Text Reader

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 tool launches Chrome with a visible window, but doesn't cover critical aspects like whether it requires user permissions, what happens if Chrome is already running (e.g., opens new window or reuses existing), error conditions, or platform dependencies. This leaves significant gaps for a mutation tool.

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 in Chinese that directly states the tool's function without any fluff. It's front-loaded with the core action and includes a useful detail (visible window) that adds value without verbosity.

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 tool's complexity (a mutation that launches an external application) and the lack of annotations and output schema, the description is insufficient. It doesn't explain what happens on success (e.g., returns a process ID or status), failure modes, or integration with sibling tools, leaving the agent with incomplete operational 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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and the baseline for 0 parameters is 4, as it avoids unnecessary information.

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 action ('手动启动' - manually launch) and target resource ('Chrome浏览器' - Chrome browser), with the additional detail of creating a visible window. It doesn't distinguish from sibling tools like 'close_browser' or 'get_browser_status', but the purpose is unambiguous.

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. It doesn't mention prerequisites (e.g., Chrome must be installed), when it's appropriate versus automated launches, or how it relates to sibling tools like 'navigate_to_page' which might require a browser to be running first.

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