Go Forward

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

Adds context beyond annotations by noting that navigation can reissue requests and expose credential-bearing page state. Annotations already indicate destructiveHint=true; description reinforces sensitivity.

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?

Three focused sentences with no repetition or fluff. Each sentence adds value: usage scenario, preconditions, and behavioral sensitivity.

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?

Covers key aspects for a navigation tool: purpose, preconditions, sensitivity. Output schema exists to handle return values, so explanation is sufficient. Minor omission: no mention of waiting for navigation to complete, but waitUntil parameter implies it.

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 coverage is 0%, and the description does not explain the two parameters (timeoutMs, waitUntil). The agent must infer meaning from names and enums alone, making parameter usage less clear.

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?

Clearly states the tool is for forward history navigation, specifying exact use cases like reproducing cached states, redirects, or SPA history issues. Distinguishes from siblings by being the only forward navigation tool.

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?

Provides preconditions (active page with forward history) and post-navigation suggestions. However, does not explicitly state when not to use or compare to alternatives like browser_go_back or browser_navigate.

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