navigate_history

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

The description notes that 'UIDs become stale', a behavioral side effect beyond the annotations' readOnlyHint=false. This adds useful context for the agent, though other potential effects (e.g., page state changes) are not mentioned.

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 front-loaded purpose and a side effect. No filler or redundant information.

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 one-parameter navigation tool, the description covers the action and a key side effect (stale UIDs). It could elaborate on the effect on the current page or history stack, but it is largely sufficient.

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 has 100% description coverage for the single parameter, so baseline is 3. The description does not add any additional meaning beyond what the schema already provides ('back or forward').

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 states verb 'Navigate' and resource 'history back/forward', clearly indicating the tool's function. It distinguishes from sibling 'navigate_page' which likely goes to a specific URL, but does not explicitly highlight this distinction.

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 guidance is provided on when to use this tool versus alternatives like navigate_page. The description lacks explicit when-to-use or when-not-to-use context.

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