move_file

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states the action but does not mention overwrite behavior, whether it is destructive, permissions required, atomicity, or what happens if the destination exists. For a mutation tool, this is a significant gap.

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?

The description is a single concise sentence that is front-loaded with the core action and resource. It contains no filler words, redundancy, or irrelevant details. It is appropriately sized for the simple operation it describes.

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 being a seemingly simple operation, the tool has no output schema and no annotations. The description does not explain return values, error handling, whether the move is synchronous, or effects of the optional 'distro' parameter. Given the environment is WSL, more context is needed for the agent to invoke 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 0%, yet the description provides no explanation of 'from', 'to', or 'distro' parameters. While 'from' and 'to' are self-explanatory, 'distro' is ambiguous without additional context. The description must compensate for the missing schema descriptions, but it fails to do so.

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 uses specific verbs 'move or rename' and identifies the resource as 'a file/directory within WSL'. This clearly distinguishes it from siblings like write_file, edit_file, or delete_path, and the scope 'within WSL' adds precision.

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 description gives no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios like copying, overwriting, or cross-filesystem moves. The context of 'move or rename' implies a distinct operation, but the tool does not state this.

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