forward

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 states 'Browser forward.' without explaining what action occurs (e.g., history navigation), whether it affects the current session, or any side effects. The agent is left without information on what to expect.

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 brief, but this is under-specification rather than effective conciseness. It lacks essential details about the tool's purpose, making the single sentence unhelpful. It does not front-load any key information because there is no informative 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 that this is a browser navigation tool with no output schema and no annotations, the description is severely incomplete. An agent cannot infer when to use it, what it does beyond a vague 'forward', or what the expected result is. The tool likely requires explanation of history navigation and session 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 100%, meaning both 'lease' and 'session' are documented in the input schema. According to calibration guidance, the baseline is 3 when schema coverage is high. The description adds no additional meaning beyond what the schema already provides, but it does not contradict or confuse parameter usage.

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 'Browser forward.' is essentially a restatement of the tool name with the word 'browser' added. It does not specify what 'forward' means (e.g., navigate to next page in history) nor does it distinguish from siblings like 'back' or 'go'. This is a tautology, providing no additional clarity to the agent.

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 such as 'back', 'reload', or 'go'. The description does not mention any context, preconditions, or scenarios where forward is appropriate. No exclusions or alternatives are indicated.

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