browser_navigate

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

With no annotations, the description must fully disclose behavior. It mentions returning a 'marked viewport' and constrains the URL to absolute HTTP(S), but does not explain how tab_id/session_id affect navigation, side effects on the current page, or what 'marked' entails. This is under-specified for a state-changing operation.

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?

Single sentence, front-loaded with the action, no redundancy. Every word adds information though 'marked viewport' is somewhat opaque, but the structure is appropriately concise.

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?

The tool has an output schema and parameters but no annotations. The description does not explain return format, prerequisites like an active session, or how this fits into the browser workflow. It is minimally viable but leaves significant gaps for an agent.

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%. The description only hints at URL format ('absolute HTTP(S)') but fails to explain tab_id and session_id, which are critical for targeting the correct browser context. The parameters are completely undocumented in prose.

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?

Description states a specific action ('Navigate'), target ('absolute HTTP(S) URL'), and result ('marked viewport'). This clearly distinguishes it from sibling tools like browser_scroll or browser_click_mark.

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?

Usage is implied by the verb 'Navigate' and the URL parameter, but no explicit guidance is provided about when to use this tool versus alternatives like browser_session_create or browser_act. No preconditions or exclusions are mentioned.

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