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

Annotations only give the generic profile (readOnly=false, openWorld=true, idempotent=false, destructive=false); the description goes well beyond them by disclosing the verify-then-fallback contract, the URL-change verification step, the fallback to the tracked next URL, and that failures surface a `via` plus `reason` instead of a false navigated:true. That is exactly the non-obvious runtime behavior an agent needs.

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?

Effectively one dense but well-formed sentence that front-loads the action, then the portability claim, then the behavioral contract. Nothing is redundant with the title or schema, and no sentence is wasted.

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?

With no output schema, the description usefully characterizes the response shape (navigated, via, reason) and the failure semantics, plus cross-platform scope. It leaves the return payload's exact structure and the socket/pageId selection rules unspecified, which is a minor gap for a 4-parameter tool.

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%, so udid, pageId, socket and the deprecated platformVersion are already documented in the schema. The description adds no parameter-level detail (e.g., how pageId is auto-picked, or when to set socket), so the baseline 3 applies.

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?

States a specific verb and resource ('Navigate the device browser forward one entry in its session history (history.forward())') and explicitly names the sibling it mirrors, webpage_back. The cross-platform note ('works on BOTH iOS Safari and Android Chrome') separates it from the web_* and ios_safari_*/android_devtools_* browser families in the sibling list.

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?

Clear usage context: this is the forward-direction counterpart to webpage_back, and the description implies you use it to move forward in history rather than navigate to an arbitrary URL (webpage_navigate/device_navigate_url). It does not spell out explicit exclusions or when the fallback-to-direct-URL path should be preferred, so it stops short of a 5.

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