restore_plotMoves a trashed plot out of Trash and returns it to its original folder when that folder still exists.
Take a plot out of the Trash, back into its folder if that still exists.
| Name | Required | Description | Default |
|---|---|---|---|
| plot_id | Yes | A plot id from list_plots or save_plot. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate the operation is idempotent and non-destructive, so safety is covered. The description adds useful context that the plot returns to its original folder if it still exists, but it does not say what happens if the folder no longer 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?
The description is a single concise sentence that front-loads the core action and includes the key conditional folder behavior. It contains no wasted text.
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 simple restore operation with one fully documented parameter and clear annotations, the description is mostly complete. The only notable gap is the fallback behavior when the original folder no longer exists.
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?
There is only one parameter, and the schema fully documents it with a clear source ('list_plots or save_plot'). The description adds no additional meaning beyond the schema, which is acceptable at 100% schema coverage.
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: taking a plot out of the Trash. It distinguishes the operation from delete_plot by emphasizing restoration, though it does not explicitly name alternatives.
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 implies the tool is used when a plot is in the Trash and needs to be restored. It does not specify when to use this versus other plot tools or any prerequisites such as required permissions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.