Rollback Transaction

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

Annotations already set destructiveHint=true, and the description reinforces this with a warning and details about COM and ezdxf behavior. There is no contradiction. The description adds some context but doesn't go beyond the annotations significantly.

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 description is extremely concise, with only two short paragraphs. Every sentence adds value: the first states the purpose, the second provides implementation-specific notes, and the third is a clear warning. No wasted 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?

Given the simple nature of the tool (no parameters, a single action), the description is fairly complete. It explains what it does and warns about destructiveness. There is an output schema but its contents are not shown; however, the description doesn't need to cover return values for such a straightforward operation.

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 tool has zero parameters, and the input schema is empty with 100% schema coverage. The description does not need to explain parameters, and it appropriately omits parameter details. Baseline for 0 params is 4.

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 it rolls back to transaction_begin, using a specific verb and resource. It mentions COM and ezdxf variations, giving some context. However, it doesn't explicitly distinguish from sibling tools like transaction_commit or drawing_undo, which could cause confusion.

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?

The description includes a warning that it is destructive and loses all changes since transaction_begin, giving a clear context for use. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like transaction_commit.

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