Reorder a tab

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

Annotations already declare this is not read-only, and the description is consistent with a mutation operation. It adds useful behavioral context by describing the operation as tab-strip drag-and-drop performed without the mouse and naming the underlying tab-move mechanisms, though it does not discuss failure modes or side effects such as active-tab changes.

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?

Front-loads the core action and then explains target modes efficiently in three short sentences. The final parenthetical API names are slightly implementation-heavy, but they still reinforce that this is a low-level tab-strip reorder.

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 relatively simple reorder tool with a fully described schema and no output schema, the description covers what the tool does and how target modes work. It could be more complete by explicitly contrasting sibling tab-move tools, but no essential calling information is missing.

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 100%, so the schema already documents all four parameters. The description mirrors the same conditional guidance for target modes and 0-based indexing rather than adding syntax, validation, or edge-case behavior beyond the schema.

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?

States a specific verb and resource: moving a tab to a new position in the tab strip. The 'tab strip' scope distinguishes it from siblings like browser_move_tab_to_window or browser_move_tab_to_group, though it does not explicitly name those alternatives.

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?

Explains how to use each target mode, especially before/after with a reference and index with a 0-based position. However, it does not explicitly say when to choose this tool over related sibling tools for moving tabs between windows, groups, or containers, leaving that inference to the reader.

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