Move an asset to a target directory within your ZenNotes vault. Specify the asset's current path and the destination folder to keep your notes organized.
Deplace un asset.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| target_dir | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, but it only repeats the operation implied by the name. It does not disclose effects like whether the source is removed, whether target_dir must exist, or what happens on conflict.
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 short clause with no wasted words, but it is under-specified to the point of being a restatement of the tool name. It lacks the structure needed to convey any additional context.
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?
Although the tool is simple and an output schema exists, the description does not explain parameter roles, prerequisites, or behavioral consequences. Given no annotations and no schema descriptions, this is insufficient for confident invocation.
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%, and the description adds nothing about the required 'path' and 'target_dir' parameters. The agent must infer that path is the asset to move and target_dir is the destination; no meaning is supplied beyond the property titles.
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?
Description 'Deplace un asset' states a specific verb (move) and resource (asset), which distinguishes it from sibling tools like move_note, rename_asset, and delete_asset. It does not add details like destination semantics, but the core purpose is clear.
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 is provided about when to use this tool instead of alternatives such as move_note, duplicate_asset, or rename_asset. The description only states the action, leaving selection entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.