undo

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

No annotations exist, so description carries full burden. It discloses coarse granularity, limitation regarding MCP steps, inability to recover lost documents, and truthful return values. This is exceptionally transparent.

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?

Bilingual repetition adds length, but each sentence adds value. Core purpose is front-loaded. Warnings and return info are clearly separated.

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?

No output schema, but description fully explains return format and meaning. Sibling tools are all different, so no missing context. Complete for a parameterless undo tool.

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, so schema coverage is 100% (vacuous). Baseline is 4. Description adds no parameter info needed.

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 'Deshacer el ÚLTIMO paso de SolidWorks (Ctrl+Z / EditUndo2)', clearly specifying the verb (undo), resource (SolidWorks last step), and scope. It distinguishes from siblings as it is a generic undo, not a specific feature tool.

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 warns that undo is coarse, may not correspond to last MCP call, and advises to verify after using. It also states what it cannot do (recover closed/lost documents). Provides clear when-to-use and when-not-to-use guidance.

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