Browser MCP Server

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. While it mentions what information is returned (documentation, return values, examples, caveats), it doesn't describe important behavioral aspects like whether this is a read-only operation, what format the documentation comes in, whether there are rate limits, or what happens if an invalid tool name is provided.

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 that front-loads all key information. Every word earns its place by specifying what the tool provides and for what scope. There's zero waste or redundancy.

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 single-parameter lookup tool with no output schema, the description provides adequate but minimal context. It tells what information will be returned but doesn't address format, structure, or error conditions. Given the complexity of browser tools and the lack of output schema, more detail about the return format would be helpful.

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 the single parameter 'toolName' well-documented in the schema. The description doesn't add any additional parameter semantics beyond what the schema already provides (e.g., format examples, validation rules, or special considerations for tool name selection).

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 with specific verbs ('Get detailed documentation, return values, examples, and caveats') and identifies the resource ('any browser tool'). It distinguishes itself from all sibling tools which perform browser operations rather than providing documentation about them.

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 documentation for browser tools - but doesn't explicitly state when to use this versus alternatives (like reading general documentation or trial-and-error). It provides no guidance on prerequisites or exclusions.

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