pcloud_rename_folderRename or move a folder in pCloud to reorganize cloud storage. Specify the current path and the new destination to update folder location or name.
Rename or move a folder in pCloud.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| to_path | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v2.5.0Input schema / additionalPropertiesAdded value: +falseOutput schema / descriptionRemoved value: -"Generic wrapper for non-object return types."v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must fully disclose behavioral traits. It only states the action without mentioning any side effects, such as whether the move overwrites existing folders, requires specific permissions, or is reversible. This is a significant gap for a mutating 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?
The description is a single sentence with no wasted words, but it is under-specified. Like the 'process' example, this is not conciseness but a lack of essential detail, so it earns a low score on structure.
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 having an output schema, the description does not clarify which parameter is which, nor does it mention any return values or error behavior. For a simple tool with two parameters and no annotations, this is incomplete; an agent would need to guess the parameter roles.
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?
The schema has 0% description coverage, and the description adds no meaning to the parameters 'path' and 'to_path'. It does not explain that 'path' is the source and 'to_path' is the destination, nor any format or constraints, leaving the agent without the necessary information to invoke the tool correctly.
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 (rename/move) and resource (folder) in pCloud, distinguishing it from siblings like pcloud_rename_file. It is clear about the general action but does not explicitly clarify the roles of the two parameters or any constraints, so it is not fully detailed.
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?
No guidance on when to use this tool versus alternatives such as pcloud_copy_folder or pcloud_delete_folder. The description provides no usage context, exclusions, or conditions, leaving the agent to infer when this tool is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.