Search recorded browsing history to locate previously visited pages, sorted newest first. Filter results by time window and limit to retrieve relevant entries quickly.
Search recorded navigation history (most recent first)
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | ||
| limit | No | ||
| query | No |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral transparency burden. It discloses the recency ordering, but does not state whether it returns full-page snapshots, metadata only, how query matches, or how hours/limit affect behavior. This is adequate for a simple read-only search tool, but leaves gaps.
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?
A single, front-loaded sentence with no filler. It efficiently communicates the tool's purpose and ordering behavior.
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 tool with three parameters, no annotations, and no output schema, the description is too sparse. It does not clarify parameter semantics, result format, or how the hours filter and limit are applied, leaving important context for an agent to call it correctly.
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 description coverage is 0%, so the description must compensate for the three parameters. It does not explain the meaning or interaction of hours, limit, and query. The parameter names and schema defaults provide some clues, but the description itself adds no parameter-level meaning.
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?
States a clear verb ('Search') and resource ('recorded navigation history'), and adds useful ordering information ('most recent first'). It is distinguishable from navigation and tab-search siblings, though it does not explicitly differentiate itself from navigate_history.
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 about when to use this tool versus alternatives such as navigate_history, search, or bookmark_search. The intended context must be inferred entirely from the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.