browser_navigate_back

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

Annotations already mark this as destructiveHint=true (history is lost), which is appropriate. Description adds 'Go back' context. However, it doesn't clarify if this closes modals or dialogs opened by the page, or what happens to page state. Not penalty for lack of explicit behavioral details given annotations already cover the key behavioral aspect.

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?

Single, clear sentence with no extraneous text. Every word earns its place.

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 zero-parameter tool with clear annotations and a simple navigation purpose, this is largely complete. However, could mention that it only works when there's a history entry (e.g., after a navigation) to avoid no-op calls. Out of 64 sibling tools, this is sufficiently distinct.

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 are defined, so description doesn't need to add parameter meaning. Schema coverage is 100% (naturally, with zero params). Baseline 4 for no params, but this is a perfect fit—description tells the agent all it needs.

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 clearly states the verb 'Go back' and resource 'previous page in the history'. It distinguishes from siblings like browser_navigate (which goes to a new URL) and browser_resume (which continues execution). Slight deduction for not specifying whether this only applies to the current tab or all tabs.

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 explicit guidance on when to use this vs alternatives. From context, it's implied for navigation history, but no mention of when not to use (e.g., if browser has no history, or if a fresh navigation should be used instead).

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