navigate_history

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

Description discloses that UIDs become stale after navigation, a key behavioral side effect. This adds value beyond the annotation 'readOnlyHint: false', which only indicates non-read-only nature.

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?

Extremely concise at five words. For a simple tool, this is appropriate; however, it lacks explicit sections or formatting that could aid scanning.

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?

Tool is simple with one parameter, no output schema. Description provides essential information: action and side effect. Slight improvement could be made by clarifying return value or error conditions, but 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?

Input schema covers 100% of parameters with enum documentation. Description does not add new meaning beyond the schema, so baseline 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?

Description clearly states 'Navigate history back/forward' with a specific verb and resource. It distinguishes from sibling 'navigate_page' by focusing on history navigation, and adds a warning about UIDs becoming stale.

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?

Minimal guidance: no explicit mention of when to use this tool versus alternatives like 'navigate_page'. The stale UID warning is helpful but doesn't provide usage context.

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