rnw_navigate

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that a browser session is created if none exists, which is a key side effect. However, it does not describe failure behavior, authentication requirements, or whether the navigation blocks until page load.

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 concise sentences with zero waste. The primary action is front-loaded, and the secondary session-creation clause follows immediately.

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 single-parameter navigation tool with no output schema and no annotations, the description covers the core action and the important session-creation side effect. It lacks some behavioral detail, but the simplicity of the tool means little else is strictly needed.

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?

There is only one parameter, and schema description coverage is 100%, documenting 'url' as 'The URL to navigate to.' The description adds no format or syntax details beyond the schema. Baseline 3 is appropriate when the schema itself fully documents the parameter.

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 to a URL in the browser.' This clearly identifies the tool's action. It does not explicitly differentiate itself from siblings like rnw_tabs_new or rnw_click, which also affect browser state, but the navigational focus is distinct enough for an agent to select it.

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?

The description implies usage by describing the action and the session-creation behavior, but it does not state when to use this tool versus alternatives such as rnw_tabs_new or rnw_click. No exclusions or prerequisites are given beyond the implicit need for a URL.

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