MCP Chrome Google Search

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

No annotations are provided, so the description carries the full burden. It mentions Chrome browser automation and returning main content text with optional links, but lacks critical behavioral details: it doesn't specify if this is a read-only operation, potential rate limits, authentication needs, error handling for inaccessible pages, or what 'readable text' entails (e.g., stripping HTML, handling dynamic content). The description adds some context but leaves significant gaps for a tool interacting with external webpages.

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 concise and well-structured with a clear opening sentence followed by a bullet point. Every sentence earns its place by stating the core purpose and a key feature. However, the bullet point format is slightly redundant with the main sentence, and it could be more front-loaded by integrating the optional links feature into the initial statement.

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 web scraping (external interactions, potential failures) and lack of annotations or output schema, the description is incomplete. It doesn't explain return values beyond 'main content text and optionally links', leaving the agent uncertain about output structure, error responses, or behavioral constraints like timeouts or permissions. For a tool with no structured safety hints, this is inadequate.

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%, with clear descriptions for both parameters in the schema itself. The description adds minimal value beyond the schema: it mentions 'optionally links' which aligns with the 'includeLinks' parameter but doesn't provide additional semantic context. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 tool's purpose: 'Extract readable text content from a webpage using Chrome browser automation.' It specifies the verb (extract), resource (text content from a webpage), and method (Chrome browser automation). However, it doesn't explicitly differentiate from its sibling 'web-search' tool, which likely searches rather than extracts content from a specific URL.

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 mentions 'optionally links' as a feature but doesn't clarify scenarios where including links is beneficial or when to choose this over 'web-search'. There's no mention of prerequisites, limitations, or typical use cases.

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