export_dxf

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

No annotations are provided, so the description carries the full transparency burden. It only states the operation and destination, without disclosing side effects (e.g., file overwrite behavior), success/failure return values, or any prerequisites. This is a significant gap for an export operation.

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 sentence with no filler words. It is front-loaded with the action verb and includes all necessary information (action, object, format, destination) in a compact form. No wasted text.

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 tool is simple with one parameter, and the description covers the core purpose. However, with no annotations or output schema detail, the description lacks behavioral context (e.g., what happens on success, whether the file is overwritten) that would make it fully complete for an export operation.

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 provides no description for 'path' (0% coverage). The description adds meaning by indicating that 'path' is the destination file path for the DXF export, which is helpful. However, it doesn't specify path format or extension requirements, but the added context is valuable for a single parameter.

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 action ('Export'), the resource ('the drawing'), the format ('ASCII DXF'), and the destination ('path'). This is a specific verb+resource+format combination that distinguishes it from siblings like export_pdf and save_as_dwg.

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 usage for DXF export but does not explicitly mention alternatives or when not to use this tool. The sibling list includes other export/save tools, but no comparative guidance is provided, so the agent must infer based on the tool name and format mention.

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