Browserbase 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. It discloses key behavioral traits: it extracts from the 'current web page', works best with 'clear, specific instructions' and a 'well-defined JSON schema', and ensures data is 'properly structured and usable'. It doesn't mention error handling, performance, or authentication needs, but covers core functionality well.

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 appropriately sized and front-loaded with the core purpose in the first sentence. Each subsequent sentence adds value: ideal use cases, when to use vs. alternatives, and best practices. It could be slightly more concise but remains efficient with zero waste.

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 no annotations, no output schema, and a single parameter with full schema coverage, the description is reasonably complete. It explains what the tool does, when to use it, and best practices. It doesn't detail return values or error cases, but for a 1-param extraction tool, this is adequate.

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 the 'instruction' parameter thoroughly. The description adds minimal value beyond the schema by emphasizing 'clear, specific instructions' and 'well-defined JSON schema', but doesn't provide additional syntax or format details. Baseline 3 is appropriate given 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 clearly states the tool's purpose: 'Extracts structured information and text content from the current web page based on specific instructions and a defined schema.' It uses specific verbs ('extracts', 'scraping', 'gathering', 'pulling') and distinguishes from sibling tools like 'observe' for interactive elements.

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 explicitly states when to use this tool ('when you need to get text content, data, or information from a page') and when not to use it ('For interactive elements like buttons, forms, or clickable items, use the observe tool instead'). It provides clear alternatives and context.

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