browser_go_forward

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention what happens when there is no next page (e.g., no-op, error), whether it preserves state, or if it has any side effects. The simple statement lacks crucial behavioral context.

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 one short, clear sentence with no unnecessary words. It is appropriately sized for a zero-parameter navigation action, achieving maximum conciseness without losing intended meaning.

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 the simplicity of the tool (no params, no output schema), the description is minimally acceptable but incomplete. It does not specify that 'forward' refers to browser history, nor does it mention behavior when no forward entry exists. This context would help the agent use the tool correctly.

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?

The tool has zero parameters and the schema properties are empty, so the baseline is 4. The description adds no parameter details, but none are needed. The schema already covers parameter semantics fully.

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 'Go forward to the next page' uses a specific verb and resource, and the sibling tool 'browser_go_back' helps clarify that 'forward' refers to browser history navigation. However, it does not explicitly mention 'history', which could cause slight ambiguity with general 'next page' concepts.

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 'browser_navigate' or 'browser_go_back'. The tool name implies forward history navigation, but the description does not state any conditions or exclusions, leaving the agent to infer usage.

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