maya_undo

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

With no annotations, the description reveals that maya_execute calls are grouped into a single undo step, so steps=1 reverts the last call entirely. It also constrains steps to 1-50, but doesn't mention side effects like redo history clearing or behavior for non-maya_execute edits.

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?

Three compact sentences plus an Args line cover everything with zero filler. The main action leads, followed by usage context and parameter meaning.

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 one-parameter undo tool with no output schema, the description provides purpose, usage guidelines, grouping behavior, and parameter meaning—complete and self-contained.

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 provides no description for steps, but the description defines it as '되돌릴 단계 수' (number of steps to revert) and lists the valid range 1-50, fully compensating for the schema gap.

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 opens with '직전 작업을 되돌립니다' (reverts the previous operation), a clear verb+resource statement. It explicitly ties to maya_execute, distinguishing it from the many sibling Maya tools.

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 states 'maya_execute 로 한 작업이 잘못됐을 때 호출하세요' (call when a maya_execute operation goes wrong), providing explicit when-to-use context. It also explains how steps map to undo groups, giving practical guidance beyond the schema.

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