restore_diagramDeprecated: use restore_document instead; this name is removed on 2027-04-30. It takes the same input as restore_document.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The document id. | |
| url | Yes | Link that opens the document in the livediagram editor. | |
| name | Yes | The restored document name, or null if unknown. | |
| restored | Yes | Always "document": tabs have no Trash. |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesAdded value: +{}Input schema / properties / documentIdRemoved value: -{
- "description": "The document to restore (from list_trash).",
- "type": "string"
-}Input schema / requiredRemoved value: -[
- "documentId"
-]Input schema / properties / diagramIdRemoved value: -{
- "description": "The diagram to restore (from list_trash).",
- "type": "string"
-}Input schema / properties / documentIdAdded value: +{
+ "description": "The document to restore (from list_trash).",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "diagramId"
-]New value: +[
+ "documentId"
+]Output schema / properties / id / descriptionPrevious value: -"The diagram id."New value: +"The document id."Output schema / properties / name / descriptionPrevious value: -"The restored diagram name, or null if unknown."New value: +"The restored document name, or null if unknown."Output schema / properties / restored / constPrevious value: -"diagram"New value: +"document"Output schema / properties / restored / descriptionPrevious value: -"Always \"diagram\": tabs have no Trash."New value: +"Always \"document\": tabs have no Trash."Output schema / properties / url / descriptionPrevious value: -"Link that opens the diagram in the livediagram editor."New value: +"Link that opens the document in the livediagram editor."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered and nothing here contradicts it. The description adds the useful facts that it is an alias scheduled for removal and that it accepts the same input as restore_document, but it says nothing about what restoring actually does (e.g. where the item reappears, side effects on shared links).
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?
One sentence, front-loaded with 'Deprecated', followed immediately by the replacement and the deadline. Every clause earns its place and there is no filler.
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?
An output schema exists, so return values need no explanation, and for a zero-parameter deprecated alias the description covers the decisions an agent must make. The only omission is a plain-language restatement of the operation, which the name and title already supply.
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 declares zero parameters at 100% coverage, so the baseline is 4. The note that it 'takes the same input as restore_document' adds a small but real pointer for an agent that knows that tool's signature.
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 never states the operation in its own words; the purpose is carried by the name/title ('Restore a document from the Trash'). It does, however, unambiguously distinguish itself from the sibling restore_document by declaring itself a deprecated alias, so an agent can route correctly without opening the schema.
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?
It explicitly names the alternative ('use restore_document instead') and gives the removal date (2027-04-30), which is exactly the when-not-to-use and replacement guidance an agent needs. Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.