agent-browser-mcp

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 mentions 'real-browser JS navigation' which hints at implementation but doesn't cover critical aspects like whether navigation blocks execution, error handling, permission requirements, or side effects. For a navigation tool with zero annotation coverage, this leaves significant gaps.

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 the core functionality ('Navigate the current tab to a URL') and adds technical context ('using real-browser JS navigation') without unnecessary words. Every element serves a purpose.

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 moderate complexity (navigation with 3 parameters), no annotations, and the presence of an output schema, the description is minimally adequate. It states the core action but lacks details about parameters, error conditions, and behavioral traits that would be needed for full contextual understanding.

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 0%, so the description must compensate for undocumented parameters. It doesn't mention any parameters at all, failing to explain 'url' requirements, 'session_id' purpose, or 'timeout' behavior. However, with only 3 parameters and a clear primary action, the baseline remains at 3 despite the lack of parameter explanation.

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 action ('Navigate') and target ('current tab to a URL'), with specific implementation details ('using real-browser JS navigation') that distinguish it from simple URL opening. However, it doesn't explicitly differentiate from sibling tools like 'open_new_tab' or 'switch_tab', which prevents a perfect 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 like 'open_new_tab' or 'switch_tab', nor does it mention prerequisites or constraints. It states what the tool does but offers no context for selection among the many browser automation siblings.

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