ghost_tab_navigate

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

With no annotations, the description carries the full behavioral disclosure burden. It meaningfully reveals that navigation happens in a background tab, does not change the user's view, and waits for load. It does not cover failure handling or timeout behavior, but the disclosed traits are significant and not inferable from the schema.

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 short sentences with no filler. The core action is front-loaded, and the second sentence adds critical behavioral context without redundancy.

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 four parameters, no parameter descriptions, no annotations, and no output schema, the description is too thin. It omits timeout semantics, return behavior, failure conditions, and how it relates to sibling tab tools, leaving an agent to guess important invocation details.

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 0%, so the description must compensate. It only implies the roles of 'tab' and 'url' through the verb 'Navigate', and says nothing about 'browser' or 'timeout_ms'. The meaning of timeout and the permissible URL format are left undocumented.

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 names a specific verb ('Navigate'), a resource ('a tab'), and a behavioral outcome ('wait for load'). It is clear and distinct from scroll/click/type siblings, though it does not explicitly distinguish itself from ghost_tab_open or ghost_act.

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 phrase 'Runs in a background tab; the user's view never changes' gives useful context, but there is no explicit guidance about when to choose this tool over alternatives such as ghost_tab_open, ghost_act, or ghost_tab_find. No exclusions or recommended conditions are stated.

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