dxf_dimensions

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

With no annotations, the description carries the full load and does well: it discloses file auto-creation, that the return value includes per-dimension measurement values for verification, and a substantive caveat that ezdxf preview rendering differs from AutoCAD (e.g. angular may show the supplementary angle, and CAD re-renders on open). It stops short of stating permissions or failure modes, but the behavioral disclosure is well above baseline.

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?

Content is front-loaded with the core purpose, then a well-structured field/type listing, then the return-value and rendering notes. The per-type enumeration is dense but each line earns its place; 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?

No output schema exists, yet the description compensates by explaining that the return contains per-dimension measurement values, and it flags the rendering-fidelity caveat. Combined with the thorough dims documentation, an agent has enough to invoke this correctly, though error/auth behavior remains unstated.

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% and the nested `dims` array is untyped in the schema, yet the description compensates heavily by documenting common optional fields (layer, color, dimstyle default "Standard", text) and the required fields per dimension type (linear/aligned/radius/diameter/angular). Only `path` and `dxfversion` go undescribed, which are largely self-evident.

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 ("向 DXF 图纸追加尺寸标注") and immediately notes the auto-create behavior. The dimension-oriented framing distinguishes it cleanly from sibling tools like dxf_draw, dxf_hatch, and dxf_splines without needing to name them.

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 enumerates the five supported dimension types and their required fields, which implicitly tells the agent when each is applicable, and notes auto-creation when the file is missing. However it never explicitly contrasts this tool with dxf_draw or states when-not to use it, so guidance is implied rather than explicit.

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