herdr_pane_move

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, so the safety profile is known. The description adds nothing behavioral beyond that: it does not say what happens to the source tab if it empties, whether focus follows the pane (a parameter exists for it), or whether the operation can fail/revert. No contradiction with annotations.

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?

A single front-loaded sentence with the verb first and no filler. It is efficiently sized, though for a tool with ten parameters and three distinct modes it is arguably too terse to be maximally useful.

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?

With ten parameters across three modes and no output schema, the description should explain how tab_id, new_tab, new_workspace, target_pane_id, split, and ratio combine (e.g., mutual exclusivity of the destination options). None of that mode-combination logic is present, leaving the agent to infer valid parameter combinations.

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 all ten parameters are self-documented and the baseline is 3. The description adds no syntax, constraints, or interaction rules beyond naming the destination modes that the tab_id/new_tab/new_workspace parameters already express.

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 ('Move') and resource ('a pane') and enumerates the three destination modes, which is enough to place it apart from siblings like herdr_pane_split or herdr_pane_close. It does not explicitly name or contrast those siblings, so it stops short of a 5.

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 three destinations ('another tab, a new tab, or a new workspace') imply the cases the tool covers, but there is no statement of when to use this over herdr_pane_split, herdr_tab_create, or herdr_workspace_create, and no prerequisites or exclusions.

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