Open Drawing

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

Annotations only provide a title, so the description carries the behavioral disclosure burden. It does reveal important traits: DWG is only supported on the live COM backend, .dwg paths are refused without the dwg capability, and ezdxf sniffs content rather than extensions, which can produce a document that doesn't exist in the expected format.

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 opening sentence is clear and front-loaded, but the 'T0.2:' paragraph is verbose and jargon-heavy. The mislabelled-file caveat is useful but could be stated more concisely without the changelog-style prefix.

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 one-parameter tool with an output schema, the description covers the key contextual concern: backend-dependent DWG support and the refusal behavior. It does not mention what happens to the currently open drawing, but the description and schema together are adequate for basic invocation.

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 schema describes the single path parameter with 100% coverage, including the DWG backend caveat. The description restates this information without adding new parameter-level specifics such as path format, absolute vs. relative paths, or file-existing requirements.

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?

States a specific verb and resource ('Open an existing DXF drawing file') and adds the DWG/backend condition. It is clear this loads an existing drawing, but it does not explicitly differentiate from siblings like drawing_new or drawing_save.

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 implies when to use the tool by saying 'existing drawing file', but it does not state alternatives such as drawing_new for creating a new drawing, nor does it explain when not to use this tool. The backend condition for DWG is useful but not framed as routing guidance.

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