Rename or move a remote path

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and 'rename or move' is consistent with that. The description adds the useful $HOME-relative scoping, but it does not disclose what happens when the destination already exists (overwrite vs fail), whether it can cross directory trees, or what a successful result looks like — meaningful gaps for a destructive operation.

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 well-formed sentence with the operation front-loaded and the scoping constraint immediately after; nothing could be trimmed without losing information.

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 three-parameter tool with fully documented schema and an existing annotation set, the definition is nearly sufficient. The only real omission is destination-collision behavior, which matters for a destructive move but is a minor residual gap.

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% and both 'from' and 'to' already carry 'Path relative to the authenticated user's remote $HOME directory.' The description restates that constraint but contributes no extra meaning, so the baseline 3 applies.

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?

The description gives a specific verb pair (rename/move) and an explicit resource scope (one file or directory), plus the $HOME-relative constraint. It is clearly distinguishable from read/write/delete siblings, though it never names them.

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?

Usage is only implied: the 'one file or directory' wording signals single-path operations rather than bulk moves, and $HOME-relative paths are stated. There is no explicit when-to-use versus pi_file_write, pi_path_delete, or pi_command_run, and no mention of prerequisites such as the target parent existing.

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