browser_navigate

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the non-obvious 'raw' behavior (bare image URLs open in a local viewer page #zlimg so the extension can script them), which is genuine added context. However it omits key navigation semantics: whether the call waits for page load, timeout behavior, and what happens on invalid URLs.

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 purpose sentence is front-loaded and the args are listed compactly in a docstring style. The 'raw' explanation runs long but carries real semantic value, so little is wasted.

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 core navigation primitive with no annotations and no output schema, the definition is only partially complete: it explains arguments but says nothing about post-navigation state (load completion, return value, failure modes) and does not distinguish from the ~30 navigation-adjacent siblings.

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, and it does document all three parameters: url with a concrete example, tab_id with its default, and raw with a detailed explanation of the viewer-page mechanism. Only per-parameter type/format nuance is missing, so this is strong compensation.

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+resource ('Navigate the active tab to a URL'), so an agent immediately understands this loads a page in an existing tab. It stops short of distinguishing itself from close siblings like browser_new_tab, browser_back, or browser_reload_tab, which would have sharpened selection.

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?

There is no explicit when-to-use guidance or exclusion. The note that tab_id 'Defaults to active tab' hints at multi-tab usage, but it never tells the agent when to prefer this over browser_new_tab or browser_click_and_wait_navigation, leaving routing to inference.

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