move_firefox_tab

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

Discloses key behaviors: verification after the move and fail-safe handling of ambiguous matches. With no annotations, this description carries the full burden and adequately covers the operation's main side effects and error handling.

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 concise and front-loaded with the action and key constraints, consisting of two clear sentences without unnecessary detail.

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?

The description covers the action, the scope (same window), verification, and failure behavior. No output schema exists, so return details are not required. It is complete for this operation.

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 schema already provides detailed descriptions for selector and index. The description adds no new parameter semantics beyond echoing 'exactly identified tab', which is redundant given the high schema coverage.

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?

Clearly states the tool moves one exactly identified tab to a target position within its own window, with verification and fail-safe on ambiguous matches. This distinguishes it from sibling tools like move_firefox_tab_to_group or move_firefox_tab_to_window.

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?

Provides clear context by specifying 'within its own window' and mentions verification and fail-safe behavior, but does not explicitly compare to alternatives or state 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.