Export DXF

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

With no readOnly or destructive annotations, the description carries the full burden of behavioral disclosure. It clearly states the primary effect (creating a DXF file from the current drawing), but it does not disclose whether an existing file at the path is overwritten, whether the drawing remains unchanged, or how failures are handled.

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 a single, front-loaded sentence with no filler. Every word contributes to identifying the action, the target, and the output format.

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 export operation with an output schema available, the description plus the schema is sufficient for an agent to call it correctly. It covers the key context (current drawing, DXF format, required path), though it does not touch on overwrite behavior or prerequisites beyond the current drawing.

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 provides 100% coverage with the path parameter described as 'Output .dxf file path'. The description adds no additional meaning to the parameter beyond what the schema already states, so the baseline of 3 is appropriate.

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 uses a specific verb ('Export'), a clear resource ('the current drawing'), and an explicit output format ('DXF file'). This differentiates it from the sibling drawing_export_pdf and other drawing management tools without relying on the schema.

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 phrase 'current drawing' implies the tool should be used when a drawing is active and the user needs DXF output, which provides clear context. However, it does not mention alternatives like drawing_export_pdf or drawing_save_as, nor does it state exclusions or conditions for choosing this tool over those siblings.

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