Open Drawing

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

Annotations provide only a title, so the description carries the full transparency burden. It discloses a non-obvious behavior: ezdxf sniffs content rather than extensions, meaning a mislabelled DXF-in-a-.dwg would be parsed and return a document that doesn't exist in that format. This adds valuable insight beyond the basic 'open' action, though it doesn't mention success/failure responses or side effects.

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 mostly concise, with the core purpose in the first sentence and a valuable technical caveat in the second paragraph. The 'T0.2' version marker is unnecessary noise, but the overall structure is effective in front-loading the primary action and then detailing important edge-case behavior.

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 simple one-parameter open tool, the description covers the primary use case, the conditional DWG support, and a subtle parsing gotcha. With an output schema present, there is no need to explain return values. The description is complete enough for an agent to correctly invoke the tool and understand when it will fail.

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 already provides a rich description for the single 'path' parameter, covering the .dxf/.dwg distinction and backend requirements (100% coverage). The description itself does not add new parameter details beyond echoing the schema, so the baseline of 3 applies.

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's action: 'Open an existing DXF drawing file.' It also specifies the conditional DWG support, distinguishing it from sibling tools like drawing_new and drawing_save. The verb and resource are explicit and immediately understandable.

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: use for existing DXF files, with DWG only on the live COM backend. It also gives a practical exclusion by stating that a .dwg path is refused on backends lacking the `dwg` capability. While it does not explicitly compare to drawing_new, the wording 'existing' implies the alternative use case for new drawings.

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