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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read profile is covered. The description adds the return shape ('new URL + title'), which is useful, but says nothing about failure modes such as no history to go back to, which is the key edge case for this action.

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 tight sentences, front-loaded with the action and followed by the return value. No waste, no redundancy.

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?

For a simple navigation action with annotations covering safety and no output schema, the description covers purpose and return shape. The remaining gap is the undocumented page_id and the missing no-history behavior, which are minor but real.

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 50%: page_id has no description anywhere, and the description omits parameters entirely. Only in_workspace is documented (in the schema). The description does nothing to compensate for the undocumented required page_id.

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+resource ('Navigate back in the page's history') and clarifies it maps to the browser back button, which distinguishes it from browser_open and other navigation siblings. It stops short of naming any alternative tool explicitly, so it doesn't reach full sibling differentiation.

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?

Usage is implied by the name and the back-button analogy, but there is no explicit when-to-use, no exclusions, and no named alternative (e.g., a forward/reload tool or browser_open). An agent can infer intent but gets no routing guidance.

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