Relocate or rename a file or folder by setting source and destination paths; end the destination with '/' to place it inside that folder under its existing name.
Move or rename a file or folder. A destination ending with '/' means 'into this folder, same name'.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Destination path, or folder ending with '/' | |
| from | Yes | Source path | |
| overwrite | No | Replace an existing destination |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses the trailing-slash destination convention, but does not explain overwrite behavior, permissions, source removal, failure modes, or what happens when the destination already exists.
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?
Two short sentences, with the core purpose front-loaded and the key destination-path rule immediately after. There is no wasted wording.
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?
The definition is adequate for a simple move operation when combined with the fully described schema. However, for a mutation tool with no annotations and no output schema, it leaves important behavioral details such as overwrite effects and error conditions unaddressed.
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 the baseline is 3. The description adds useful meaning beyond the schema by clarifying that a destination ending in '/' means 'into this folder, same name,' though it does not discuss the overwrite parameter.
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 states a specific verb and resource: 'Move or rename a file or folder.' It clearly identifies the operation, including renaming, but does not differentiate the tool from siblings such as copy or delete.
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 move rather than copy, when renaming is preferable, or what prerequisites apply. It only describes one destination-path convention, which is parameter semantics rather than usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.