navigate_back

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

No annotations are provided, and the description is only a short phrase that states the action. It does not disclose behavior such as error handling when no previous page exists, synchronization semantics, or side effects, which is a gap for a navigation action.

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 a single concise phrase that efficiently conveys the tool's purpose. It is appropriately sized for a zero-parameter navigation tool, with no unnecessary words.

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 the tool's simplicity and lack of an output schema, the description captures the core purpose. However, it omits potential edge-case behavior (e.g., navigating back from the root page), which reduces completeness slightly.

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 tool has zero parameters, so the baseline is 4. The description and schema fully cover the parameter situation (empty), and no additional parameter information is needed.

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 the action of navigating back to the previous page, using a specific verb and resource. It differentiates itself from sibling tools like navigate_to or redirect_to by focusing on backward navigation.

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?

The description offers no guidance on when to use this tool versus alternatives such as page_stack or current_page. It does not mention prerequisites, exclusions, or conditions like whether a previous page exists.

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