dxf_render

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

No annotations are provided, so the description carries the full burden. It discloses that rendering is purely local, but says nothing about whether an existing PNG at png_path is overwritten, what errors occur on a missing/invalid DXF, or any return value.

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?

Purpose is front-loaded in one sentence, followed by a compact Args block; every line carries information. Minor slack in repeating the obvious meaning of path/png_path.

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 tool that writes a file with no annotations and no output schema, the argument coverage is complete, but the description omits the behavioral essentials an agent needs: overwrite behavior on png_path and failure modes for unreadable DXF input.

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 0% schema description coverage, the description documents all four parameters and adds constraints absent from the schema: the dpi range (100~300) and accepted background values ('white'/'black'/'dark' or #RRGGBB). This fully compensates for 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?

Clearly states a specific verb+resource: rendering DXF to a PNG preview, and adds a distinguishing scoping note ('纯本地，不需要打开 AutoCAD') that separates it from dxf_open_in_autocad. Sibling dxf_export_pdf is only implicitly contrasted via output format, so it falls just short of 5.

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 'preview' framing and 'no AutoCAD needed' note imply the use case (quick local thumbnail generation), but nothing states explicitly when to choose this over dxf_export_pdf or dxf_open_in_autocad, and no prerequisites are given.

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