navigate

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

Since no annotations are provided, the description carries the burden of behavioral disclosure. It clearly reveals the underlying mechanism (CDP vs IPC) and the focus-preserving nature when a tab is specified. However, it does not mention error handling, load waiting, or permission requirements, which are relevant for a navigation tool.

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 concise, consisting of two short sentences that immediately convey the core action and the two distinct navigation modes. Every word earns its place, with no redundant information.

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 tool with only two well-described parameters, the description covers the essential behavioral distinction and does not need to explain return values absent an output schema. It omits edge cases like tab not found or navigation failure, but overall it is sufficiently complete for its complexity.

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 input schema already describes both parameters well (tab as URL/title substring with CDP semantics, url as target URL). The description adds a conditional relationship between them, explaining that the choice of transport depends on whether tab is provided, which enriches the parameter semantics beyond what the schema states.

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 clearly states it navigates a tab to a URL, and explicitly distinguishes between navigating a specified tab via CDP and the current tab via IPC. This differentiates it from sibling tools like open_tab or reload_page, which serve different navigation purposes.

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 provides explicit guidance on when to use the tab parameter (to navigate a specific tab without changing focus via CDP) versus when to navigate the current tab via IPC. It does not name alternatives such as go_back or reload_page, but the context makes the appropriate use clear.

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