herdr_pane_resize

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds no behavioral context beyond that — nothing about minimum/maximum size, how neighboring panes absorb the change, or why the operation is non-idempotent. It merely restates the mutation the annotations imply.

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 short, front-loaded sentence with no filler. It is efficient, though perhaps terse enough that some clarifying detail was sacrificed.

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 mutation tool with a fully documented 3-parameter schema and no output schema, the description is minimally adequate. However, it omits resize semantics (what 'amount' means in practice, e.g., lines/cells, and the effect on adjacent panes) that would help an agent call it correctly.

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%, with each parameter (amount, pane_id, direction) documented in the schema, including the enum for direction. The description's 'focused (or given) pane' only restates the schema's 'omit for current' note, so baseline 3 is appropriate.

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 (resize) and resource (pane), plus the direction scope, so the agent knows the operation. It does not distinguish itself from adjacent pane-manipulation siblings such as herdr_pane_split, herdr_pane_move, or herdr_pane_zoom.

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?

There is no guidance on when to use resize versus split/move/zoom, nor any stated prerequisites or constraints (e.g., whether the pane must be in a split layout). Usage is only implied by the tool name.

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