Browser MCP Server

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

No annotations are provided, so the description carries full burden. It mentions reloading but doesn't disclose behavioral traits such as whether it waits for page load, handles errors, or affects browser state. The reference to 'browser_docs' hints at more info but doesn't add transparency directly.

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 directly states the action. It's front-loaded with the core purpose, though the parenthetical reference adds minor complexity. Overall, it's appropriately sized with minimal 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 simple action with 0 parameters, the description is incomplete. It lacks details on behavior, error handling, or what 'reload' entails, making it insufficient for an agent to understand full implications without external docs.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter details are needed. The description doesn't add parameter semantics, but with zero parameters, the baseline is 4 as it adequately handles the lack of inputs.

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 states the action ('Reload') and target ('the current page'), which is clear but vague about scope. It doesn't specify what 'reload' entails (e.g., refreshing content, resetting state) or differentiate from siblings like browser_navigate. However, it's not tautological and provides a basic purpose.

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 includes a reference to 'browser_docs' for more information, implying external guidance, but offers no explicit when-to-use context. It doesn't clarify when to use this vs. alternatives like browser_navigate or browser_go_back, leaving usage ambiguous.

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