autocad_open_document

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

Annotations already establish non-read-only, idempotent, non-destructive, and non-open-world behavior. The description adds useful behavioral context: the opened drawing becomes active, .dxf uses ezdxf and .dwg uses COM, and it returns a JSON status.

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 front-loaded with the core purpose and then uses a compact Args/Returns structure. It contains no filler and is appropriately sized for a simple one-parameter tool.

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 straightforward open-document tool with annotations and an output schema, the description provides enough context to invoke it correctly: file format support, active-document side effect, and return shape. It could more explicitly route the agent away from new/initialize document tools.

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?

With only one parameter and the context signal showing low schema description coverage, the description compensates by explaining that path must be an existing '.dxf' or '.dwg' file. It adds backend-specific format meaning beyond the bare schema.

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 drawing file and make it the active document.' The word 'existing' clearly distinguishes it from sibling tools such as autocad_new_document and autocad_initialize_drawing.

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 it by saying it opens an 'existing' file, but it does not explicitly compare against new_document or initialize_drawing. No when-not or alternative routing is provided.

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