browser_navigate_back

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 only states the basic action without mentioning what happens when there is no previous page, whether it waits for the page to load, if it preserves or discards form data, or any side effects. While the action is simple, the lack of contextual behavior transparency leaves gaps for an AI agent.

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, clear sentence with no unnecessary words. It is front-loaded and directly communicates the tool's function. It earns its place by being succinct and unambiguous.

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 the tool has no parameters, no output schema, and no annotations, the description is the only source of information. It covers the high-level action but omits details about return values, behavior under edge cases (e.g., no history), and potential side effects. This is adequate for a simple tool but not fully complete for an AI agent to anticipate all outcomes.

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 accepts zero parameters, so there are no parameter semantics to explain. According to the scoring rubric, a baseline of 4 is appropriate when there are no parameters, and the description does not need to elaborate further.

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 back to the previous page' uses a specific verb ('go back') and identifies a clear resource (the previous page). It distinguishes itself from the sibling tool 'browser_navigate' which implies forward navigation to a new URL, and from 'browser_tabs' which deals with tab management.

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?

The description implies usage when the agent needs to return to the prior page in the browser history, but it does not explicitly state when to use this tool over alternatives like 'browser_navigate' or provide any exclusion scenarios (e.g., no previous page, form state loss). The context is clear enough for a simple action, but no explicit guidance is given.

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