unity_undo

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Describes operating on Unity's global undo stack and being equivalent to Ctrl+Z. With no annotations, this provides useful behavioral context. Could mention what happens when no steps are available.

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?

Two concise sentences with the core action front-loaded. No unnecessary words.

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?

Lacks explanation of return values or error behavior (e.g., what happens if undo stack is empty). Given the tool simplicity, it is adequate but not comprehensive.

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 coverage is 100% and the port parameter is fully described in the schema. The description does not add extra meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Clearly states it undoes the single most recent step on Unity's global undo stack, mimicking Ctrl+Z. Distinguishes from sibling tool unity_undo_last which reverts specific MCP actions.

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?

Explicitly says to prefer unity_undo_last for reverting a specific MCP action, providing a clear alternative. However, it does not mention prerequisites or error cases like empty undo stack.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.