MCP Browser Text Reader

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('navigate') but doesn't describe what this entails (e.g., opens a new tab/page, reloads current page, handles redirects), potential side effects (e.g., page loading delays, authentication prompts), or error conditions. This is inadequate for a tool with mutation implications.

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 ('导航到指定URL') that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 (navigation with optional waiting and timeout), lack of annotations, and no output schema, the description is insufficient. It doesn't cover behavioral aspects, return values, or error handling, leaving significant gaps for the agent to operate effectively.

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%, so the schema already documents all parameters (url, waitForSelector, timeout) with descriptions and constraints. The description adds no additional meaning beyond the schema, such as explaining interactions between parameters or typical use cases, meeting the baseline for high schema coverage.

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 '导航到指定URL' (Navigate to specified URL) clearly states the verb 'navigate' and the resource 'URL', making the purpose immediately understandable. However, it doesn't differentiate from potential sibling tools like 'get_page_info' or 'get_current_page_text' that might also involve page navigation, so it doesn't reach the highest 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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., browser must be launched), exclusions, or comparisons to sibling tools like 'launch_chrome_manually' or 'get_page_info', leaving the agent to infer usage context.

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