navigate_forwardNavigate forward in the browser history. Specify the number of steps and optionally the tab ID; defaults to the active tab.
在标签页中执行浏览器前进。
| Name | Required | Description | Default |
|---|---|---|---|
| steps | No | 前进步数 | |
| tab_id | No | 标签页 id，省略时用最新标签页 |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| message | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint: false already indicates it's not read-only. The description adds no information about side effects like loading a page, potential errors if history is empty, or interaction with tab_id.
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 a single, concise sentence with no redundant information.
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?
The description omits edge cases such as behavior when there is no forward history or when tab_id is invalid. However, for a simple navigation action, it provides the core functionality.
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?
Both parameters have descriptions in the schema (steps and tab_id), providing adequate meaning. The tool description doesn't add extra clarification, but schema coverage is 100%.
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 action: 'execute browser forward' in the tab. This distinguishes it from sibling navigation tools like navigate_back or navigate.
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?
No guidance on when to use this tool versus alternatives such as navigate_back or refresh. The description is purely a statement of functionality without context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.