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

The description adds critical behavioral context beyond the annotations. It warns that the action 'may leave unsaved form data,' which alerts the AI to a potential data loss consequence not captured by the abstract `destructiveHint: false` 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?

The definition is highly concise. It provides the action, the target, and the necessary risk disclosure in two focused sentences, placing the warning about data loss effectively.

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?

The description is highly complete. For a state-mutating tool, it covers the action, the scope (Chromium tab history), and the operational caveat (checking the state afterward), leaving the agent with all necessary context to use it safely.

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?

The schema description coverage is 100%, meaning the schema defines all technical parameters. The description mentions 'selected Chromium tab,' which semantically informs the agent about the entity being acted upon but does not add new meaning to the parameters themselves.

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 uses the specific verb 'go back one page' and clearly identifies the resource ('history of a selected Chromium tab'). This is entirely distinct from siblings like browser_forward or browser_navigate_url.

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 provides clear operational guidance by stating the user must 'choose the tab first' and 'inspect the new page state afterward.' While it doesn't list explicit alternatives, the safety warning guides appropriate usage.

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