browser_navigate

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

With no annotations, the description does provide useful behavioral context: snapshot observation has a separate deadline and observation_error does not mean navigation failed. It still omits timeout behavior, dialog handling implications, and what the navigation result contains.

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 compact and front-loaded with the primary action, then adds important caveats about file access and snapshot observation. No sentence is redundant.

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 7-parameter navigation tool with no annotations and no output schema, the description is not complete enough. It covers the main action and one error nuance, but most parameter behavior and the return/result shape remain unexplained.

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 only 29%, so the description must compensate but does not. It clarifies URL versus history-entry intent and file-access requirements, but leaves tab_handle, timeout_ms, wait_until, and most dialog_policy semantics undocumented.

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 a specific verb and resource: navigate a claimed tab to an HTTP(S)/file URL or history entry, optionally return a snapshot, and recover an about:blank tab. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as browser_open_tab or browser_fetch.

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?

It implies usage through 'claimed tab', 'history entry', and recovery from about:blank, and notes that file destinations require extension file access. However, it gives no explicit guidance on when to use this versus browser_open_tab, browser_fetch, or browser_click.

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