arc_move_tab_to_space

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

No annotations provided, so description carries full burden. It only states the action but omits critical behavioral details: does the tab close from the original space? Is it a move or copy? What if the target space doesn't exist? Does it switch focus to the target space? These gaps make agent invocation risky.

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?

Single sentence, no wasted words. However, extreme brevity sacrifices completeness. For a simple tool, it's appropriately short but could benefit from a second sentence on 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?

Despite simple schema and no output schema, description lacks essential context: what happens to the tab after move, error states, side effects. Given sibling tools like arc_list_spaces and arc_get_tabs_in_space, the agent needs guidance on workflow. Incomplete for a mutation tool.

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 coverage is 100%, so baseline is 3. Description adds no extra meaning beyond schema descriptions. It does not explain that tab_index is likely 0-based or relative to the current space, nor what format target_space expects (exact name? case-sensitive?). No examples or context provided.

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?

Description 'タブを別のSpaceに移動する' clearly states the action: moving a tab to a different Space. The verb 'move' and resources 'tab' and 'Space' are specific, and it distinguishes from siblings like arc_switch_tab (switching within same space) or arc_focus_space (focusing a space).

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. Does not mention prerequisites (e.g., tab must exist, space must exist) or compare to similar tools like arc_switch_tab or arc_focus_space. The agent receives no help in deciding between moving vs switching vs focusing.

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