go_back

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

With no annotations, the description carries full burden for behavioral disclosure. It provides no details on side effects (e.g., page reload, state loss), error handling (e.g., if no history), or return value. The tool is treated as a black box.

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 short sentence with no unnecessary words. It is perfectly concise for the tool's purpose.

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 parameterless navigation action, the description minimally covers the purpose. However, it lacks context on what 'previous page' means (browser history vs app state) and any notes about failure modes or return behavior. It is adequate but leaves gaps.

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?

There are zero parameters (schema coverage 100%). Per rules, baseline is 4. The description adds no parameter info because none are needed. It correctly implies the tool takes no input.

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 'Navigate back to the previous page' clearly states the action (Navigate back) and the target resource (previous page). It distinguishes from sibling tools like 'navigate' which goes to a new URL, but could be more specific about the navigation context (e.g., browser history stack).

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' or 'click' on a back button. There is no information about prerequisites or limitations (e.g., what happens if there is no previous page).

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