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 side effect. However, no annotations exist, and it does not mention whether the tool is destructive, read-only, or requires permissions. For a navigation action, more context would be helpful.

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 description is extremely concise with two sentences. It front-loads the purpose and adds a critical behavioral note. Every sentence adds value with 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?

Given one parameter, no output schema, and a large sibling set, the description covers the core functionality but lacks deeper context such as what 'stale' means operationally or how this differs from other page navigation tools. It is minimally adequate.

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 input schema provides 100% coverage with a clear enum description for the direction parameter. The description does not add extra meaning beyond noting UID staleness, which is not parameter-specific. Baseline score of 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 the tool navigates history back or forward, which distinguishes it from navigat_page (URL navigation). The mention of UIDs becoming stale adds specific context, but the verb and resource are clear.

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 on when to use this tool versus alternatives like navigate_page or click-based navigation. The description does not specify prerequisites or exclusions, leaving the agent without explicit decision support.

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