Begin Transaction

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

Beyond the annotations, the description reveals meaningful behavioral traits: it sets an AutoCAD undo mark in COM, saves a DXF snapshot in ezdxf, and supports rollback of subsequent operations. It also mandates pairing with commit or rollback, which is essential behavioral guidance not present in annotations.

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 compact and front-loaded with the core purpose ('Begin a transaction'). Backend differences are organized clearly under labeled sections, and the pairing requirement is a single closing sentence. No filler or redundant material.

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?

The description fully covers the tool's behavior across both supported backends and states the necessary pairing with commit/rollback. With no parameters and an output schema present, nothing essential is missing for an agent to correctly invoke and reason about this 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?

The input schema has zero parameters, so the description does not need to explain parameter semantics. With no parameters, the baseline is 4, and the description reasonably focuses on behavior rather than arguments.

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 'Begin a transaction (undo mark)', a specific verb and resource that clearly defines the operation. The backend-specific details (COM undo mark vs ezdxf DXF snapshot) further distinguish it from related transaction_commit and transaction_rollback 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?

The description provides clear context by explaining what the transaction does in both backends and explicitly states 'Always pair with transaction_commit or transaction_rollback.' It does not explicitly discuss when not to use it or compare it to drawing_undo, so it stops short of a 5.

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