browser_back

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

Without annotations, the description only states it goes back and returns a snapshot. It omits details like what happens if history is empty or if multiple steps can be taken, providing minimal 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 two sentences plus a single arg line, front-loading the core purpose with zero filler.

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 simple navigation action and existence of an output schema, the description is mostly complete. It lacks error cases but is sufficient for the use case.

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 coverage is 0%, but the description adds a brief explanation for the sole parameter: 'Target page ID'. This provides minimal extra meaning beyond the schema title.

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 clearly states 'Navigate back in browser history' using a specific verb and resource, distinguishing it from siblings like browser_forward and 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?

The description implies usage (navigating back) but does not explicitly state when to use it compared to alternatives like browser_forward or browser_navigate, nor does it mention prerequisites.

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