browser_navigate

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

With no annotations, the description carries the full burden and does add non-obvious value by disclosing that file:// is rejected unless NORACU_ALLOW_FILE_URL=1. It omits important mutation behavior: whether navigation waits for page load, what happens if no tab exists, and whether it errors or auto-opens a browser.

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?

Two short sentences, front-loaded with the action and followed by the one surprising constraint. Nothing 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 one-parameter navigation tool with no output schema, the core is covered: action, target, and the notable scheme restriction. Only the preconditions (existing tab/session) and load-completion semantics are missing.

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?

The single parameter has 0% schema description coverage, so the description must compensate. It does constrain the value to an http(s) URL, which adds meaning beyond the bare 'string' type, but gives no format, normalization, or relative-URL guidance.

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?

States a specific verb and resource ('Navigate the current tab to an http(s) URL'), and the phrase 'current tab' implicitly distinguishes it from browser_launch, which creates a session. It stops short of explicitly naming the sibling, but an agent can tell the two apart.

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 only implied: 'current tab' suggests an existing browser session must be open, but the description never says so nor directs the agent to browser_launch if none exists. The file:// restriction is a constraint rather than when-to-use guidance.

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