browser_navigate_tab

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

No annotations provided, so description carries full burden. '[Disabled]' status is disclosed, but missing critical behavioral details: whether navigation waits for page load, side effects on current page content/history, error conditions (invalid URL, closed tab), or timeout behavior.

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 efficient sentences with zero redundancy. Critical '[Disabled]' status front-loaded immediately. Prerequisite tool reference placed appropriately in second sentence. Every word earns its place.

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?

Adequate for a 2-parameter navigation tool with no output schema. Covers basic function, disabled status, and parameter prerequisite. Missing error handling details and navigation lifecycle behavior (sync vs async), but acceptable given schema simplicity.

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 has 100% description coverage ('Tab ID to navigate', 'URL to navigate to'), establishing baseline 3. Description adds context that tabId must be found via browser_list_tabs, but doesn't explain URL format requirements or validation behavior beyond schema's URI format hint.

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 specific action (navigate) and resource (existing browser tab) clearly. The '[Disabled]' prefix provides critical status context. Implicitly distinguishes from browser_open_tab by emphasizing 'existing' tab, though could explicitly contrast with sibling tools.

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?

Explicitly references sibling tool browser_list_tabs as prerequisite for obtaining tabId parameter. Provides clear workflow guidance (list tabs → navigate). Lacks explicit 'when not to use' guidance (e.g., contrast with browser_open_tab for new tabs).

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