firefox_forward

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

Without annotations, the description must disclose behavioral traits. It states the action but does not explain what happens if there is no forward history, potential side effects, or other behavioral details. The description adds minimal value beyond the name.

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 very concise, using a single sentence that is front-loaded and efficient. Every word serves a purpose, with no unnecessary information. However, it could be improved by adding a bit more detail without becoming verbose.

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 tool with one parameter and no output schema, the description is minimally adequate. It identifies the core action but lacks context about return values, error handling, or integration with other tools. It meets the baseline but has clear 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?

Although schema coverage is 100%, the parameter description in the schema is a typo ('fire-fodex session tab id') and not meaningful. The tool description does not add any context about the parameter's purpose or usage, leaving the agent with unclear semantics.

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 'Go forward in a Firefox tab' uses a specific verb and resource, clearly indicating the action. It distinguishes well from sibling tools like firefox_back and firefox_navigate, as it specifically refers to forward navigation within a tab.

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 provides no guidance on when to use this tool versus alternatives, such as when to use firefox_back vs firefox_forward, or prerequisites like needing a forward history entry. This omission limits its usefulness for an AI agent deciding between tools.

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