Restore one or more previously undone 3ds Max actions in a single command. Specify steps to reverse multiple undos, recovering work lost to accidental undo.
重做最近一次（或最近 N 次）被撤销的操作。 [English] Redo the last undone operation (or the last N).
| Name | Required | Description | Default |
|---|---|---|---|
| steps | No | 重做步数，默认 1。 | Number of steps, default 1. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotation Contradiction: annotations declare readOnlyHint=true, but redo_last is a mutation that re-applies an undone operation and changes scene state. The description provides no additional behavioral context and is contradicted by the structured safety hints.
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 definition is compact and front-loaded: one Chinese sentence and its English equivalent, with no filler or repetition beyond the bilingual translation.
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 single-parameter command, the core operation is stated, but the incorrect readOnlyHint leaves the safety profile misleading. It also doesn't clarify what happens when there is no undone operation to redo or whether the tool returns anything.
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% and the steps parameter already documents its type, range (1–50), and default. The description's 'or the last N' echoes the parameter but adds no new semantic detail.
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 clear verb ('Redo') and resource ('the last undone operation (or the last N)'), which distinguishes it from undo_last and most other sibling tools. It does not explicitly name the sibling alternative, but the 'undone operation' wording makes the purpose unambiguous.
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 given about when to use redo_last versus undo_last or other history tools, nor are prerequisites mentioned (e.g., an undo must have just occurred). The existence of undo_last in the sibling list makes this omission noticeable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.