navigate

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

The description discloses that the tool replaces the active tab's page (unless tabId is provided) and defaults to the active tab. No annotations are provided, so the description carries the burden, and it adequately covers the core behavioral trait of page replacement, though it does not mention loading progress or error states.

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 two sentences long, front-loading the core action and then providing a conditional and an alternative. Every sentence adds value.

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?

Given 3 parameters (one required), an enum, and no output schema, the description covers the main purpose, default behavior, and key alternative. It does not explain return values or error handling, but these are not critical for a navigation tool with clear schema hints.

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 description adds context beyond the input schema, such as explaining that the tabId defaults to the active tab and that the navigation replaces the current page. With 67% schema description coverage, the description supplements the remaining 33% by clarifying the tool's behavior for the url 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?

The description clearly states the tool navigates a tab to a URL, replacing the current page. It distinguishes itself from sibling tools like 'forward', 'back', and 'reload' by specifying that it navigates to a new URL, not history navigation.

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 explicitly provides an alternative: 'to open a site without losing the current page, use `tab_new` instead'. This guides the agent on when not to use this tool.

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