chrome_navigate

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'point' the tab at a URL, but reveals nothing about side effects, permissions, whether the tab changes state, or what happens if the tab is not found. This is a severe gap 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 extremely short (one sentence), but this is under-specification rather than concise efficiency. It front-loads the core action but omits all supporting details necessary for correct invocation. It does not earn its brevity by leaving out superfluous content; it leaves out essential content.

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 three parameters with no descriptions, no annotations, and an output schema that isn't referenced, the description is drastically incomplete. It provides no information about parameter usage, prerequisites, or return behavior, making it nearly impossible for an agent to call the tool correctly without additional context.

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%, and the description does not compensate. It only mentions 'different URL,' which loosely maps to the 'url' parameter, but the 'device' and 'tab_id' parameters are completely unexplained. An agent cannot know how to identify the target tab or device from this description.

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 states a clear action: 'Point an existing Chrome tab at a different URL.' It identifies the resource (Chrome tab) and the operation (navigation). It distinguishes from siblings like chrome_open (likely opening a new tab) and chrome_tabs (listing tabs) by specifying 'existing' tab, but it doesn't explicitly contrast them.

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?

There is no guidance on when to use this tool versus alternatives like chrome_open or chrome_tabs. The word 'existing' implies a prerequisite, but no exclusions or context about selecting the right tab or device is provided. An agent must infer usage from the name alone.

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