zen_forward

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

No annotations are provided, and the description does not disclose behavioral traits such as whether it is a no-op if there is no forward history, whether it causes any side effects, or if it requires certain permissions. This is a significant 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 extremely short (4 words), which is concise but lacks necessary detail. While front-loaded, it does not earn its place fully as it omits critical context about parameters and 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?

Given the simplicity of the tool (1 optional param, no output schema), the description is incomplete. It fails to mention tab scoping, failure conditions, or relationship to 'zen_back'. Despite low complexity, more completeness is needed for reliable use.

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%, and the description does not explain the tab_id parameter. The schema shows optional integer or null, but the description adds no meaning, leaving the agent to guess its purpose and impact.

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 'Go forward in history,' which is a specific action. It distinguishes from sibling tool 'zen_back' which likely goes backward. However, it does not mention that it applies to a specific tab via the tab_id parameter, leaving slight ambiguity about scope.

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 'zen_back' or other navigation tools. There is no mention of prerequisites (e.g., having visited a page before) or when not to use it.

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