navigate_history

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

The description discloses that 'UIDs become stale', a key behavioral trait beyond the readOnlyHint: false annotation. This adds meaningful context about side effects of navigation, though it doesn't elaborate on other state changes.

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 concise sentences with no wasted words. The description is front-loaded with the action and includes an important caveat in the second sentence.

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 tool is simple (one parameter, no output schema), and the description covers purpose, parameter, and a notable side effect. It is sufficiently complete for the agent to understand the basic operation, though it could mention what happens to the current page state.

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 100% with the direction parameter fully described (enum back/forward). The tool description reiterates this but adds no extra parameter detail, so baseline 3 is appropriate.

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 clearly states 'Navigate history back/forward' with a specific verb and resource, distinguishing it from sibling tools like navigate_page. The addition of 'UIDs become stale' further clarifies the scope and consequence.

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 tool versus alternatives is provided. The description implies it is for history navigation, but does not name or exclude other navigation tools, leaving the agent to infer context.

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