browser_back

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

Annotations set readOnlyHint: false, indicating mutation. Description confirms navigation action but does not disclose potential side effects (e.g., page reload, state loss) or behavior when at first page. With simple action, minimal additional transparency beyond annotation.

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?

Two words, zero waste. Every word earns its place. Perfectly concise for a simple tool.

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 no parameters and existence of an output schema, the description is mostly complete for a simple navigation action. However, it omits mention of edge cases (e.g., no previous page) or return value, but these may be documented elsewhere.

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?

No parameters in input schema, so description does not need to add parameter information. Schema coverage is 100%, meeting baseline expectation.

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?

Description 'Navigate back' uses a specific verb ('Navigate') and resource ('back'), clearly indicating the action of moving to the previous page in browser history. It distinguishes from sibling tools like browser_forward, browser_navigate, and others.

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 guidance on when to use this tool versus alternatives (e.g., browser_forward, browser_navigate). It does not mention that it only works if there is a previous page, nor does it state to use it for backward navigation only.

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