neuron_navigate

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals only the URL scheme restriction, but says nothing about whether navigation waits for page load, how failures/timeouts are reported, whether the current page state is discarded, or what side effects (script execution, network requests) may follow. For a navigation action that can hang or mutate page state, this is a significant gap.

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?

A single ten-word sentence with zero waste; the core action, target, and constraint are all present. The parenthetical constraint is efficiently placed without disrupting the main clause. Under-specification is a separate concern handled in other dimensions; as pure conciseness, this is exemplary.

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 simple two-parameter, fully-documented tool, the core 'what' is adequately covered. However, with no annotations and no output schema, the description should compensate by noting return behavior, failure semantics, or how it differs from same-family navigation tools. It is minimally viable but leaves behavioral and routing gaps an agent must guess at.

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 100% (both url and tabId have descriptions), so the baseline is 3. The description adds one piece of meaning beyond the schema—the http/https scheme restriction—which is genuinely useful, but it does not elaborate on URL format expectations or what tabId references. The schema carries the heavy lifting.

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 ('Navigate'), a precise resource ('a tab'), and a target ('to a URL'), which clearly identifies the operation. The '(http/https only)' constraint adds useful scope. It is clear but does not explicitly differentiate from siblings like neuron_open_tab (new tab) or neuron_reload (refresh), so the distinction is implied rather than stated.

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 guidance on when to use this tool versus alternatives. With siblings like neuron_open_tab, neuron_reload, and neuron_list_tabs in the same family, an agent receives no hint about which tool fits which scenario. The only constraint ('http/https only') is an input restriction, not usage guidance, so the agent is left to infer context.

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