proj_export_dxf

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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: omitting output_path may trigger a modal file-save dialog, which can stall an automated agent. It does not cover overwrite behavior, whether the export is silent by default, which layers/units are exported, or failure modes.

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?

Front-loaded with the core action, followed by the prerequisite and the one behavioral caveat. The Args/Returns scaffolding is slightly heavy for a single optional parameter, but nothing is padded.

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 output schema exists, so the return value need not be explained, and the prerequisite plus optional-parameter behavior are covered. For a format-export tool, however, an agent would still benefit from knowing what geometry/layers are included and whether an existing file is overwritten.

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?

Schema coverage is 0%, so the description must compensate for the single parameter, and it does: it specifies that output_path is a full path to a .dxf file, marks it optional, and explains the concrete consequence of omitting it. Format/encoding details of the path (e.g., relative vs absolute, extension handling) remain unstated.

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 with the target format named explicitly ('Export the active PCB to DXF (AutoCAD) format'), which implicitly distinguishes it from the sibling STEP/PDF/image exporters. It stops short of naming those siblings directly, so an agent must infer the routing rather than read it.

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 prerequisite ('Requires an active PCB document') is stated, which is real usage guidance. There is no explicit guidance on when to pick this over proj_export_step, proj_export_pdf, or proj_export_image, so the choice is left to inference from the format name.

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