undo

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

Discloses coarse behavior, honest reporting of nothing to undo (undone=False), and states it cannot recover closed/lost documents. No annotations provided, so description carries full burden.

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?

Front-loaded with core purpose and includes essential warnings. Slightly lengthy due to bilingual text, but every sentence adds value. Could be slightly more concise.

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 no-parameter tool, description covers purpose, usage, behavioral constraints, return format, and verification steps. Very complete given simplicity and lack of output schema.

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?

No parameters in schema (0 params), so no additional meaning needed. Baseline 4 is appropriate for zero-parameter tools.

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 clearly states the tool undoes the last SolidWorks step (Ctrl+Z/EditUndo2). It distinguishes from siblings like rollback_to_end/rollback_to_feature by emphasizing coarseness.

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?

Explicit warnings: undo is coarse, does not necessarily correspond to last MCP call, cannot recover closed docs; advises to capture_views after and not chain blind undos.

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