nex_browser_go_back

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

With no annotations, the description carries the full burden of behavioral disclosure, but 'Navigated back' only states a result. It does not explain browser history interactions, what happens with empty history, or side effects on page state.

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 short, but brevity here is under-specification rather than conciseness. A single vague phrase does not earn its place as a tool definition.

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?

As a navigation tool with no annotations or output schema, the description is critically incomplete. It provides no context about prerequisites, behavior with no history, or interaction with the current active page.

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 input schema fully documents both optional parameters with defaults, so the description need not restate them. However, the description adds no semantic context about how pageId/sessionId affect the back navigation.

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 'Navigated back' is essentially a past-tense restatement of the tool name, not a clear purpose statement. It fails to specify that this goes to the previous page in browser history or to distinguish from nex_browser_go_forward and nex_browser_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 usage guidance is provided. There is no indication of when to use this tool versus go_forward or navigate, nor any mention of history stack requirements or fallback behavior.

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