dxf_add_dimensions

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is covered; the description usefully adds that it produces real DIMENSION entities and defaults (dimstyle 'EZDXF'). It does not clarify whether the source DXF is modified in place or written to output_path, nor what happens to pre-existing dimensions.

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 purpose, then usage, parameters, kind schemas and an example in a scannable labeled layout with no filler sentences. The parameter block is dense but every line carries specific information, so it earns its length.

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?

An output schema exists so return values need not be described; for a mutating, four-parameter tool with untyped nested objects the description covers invocation well. Missing pieces are sibling differentiation from 'add_dimension' and the write-target semantics of path/output_path.

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 carries the full burden and largely succeeds: it lists all four parameters, documents common nested fields (layer, color, dimstyle, text_height, arrow_size, decimals, lfac, text) and gives per-kind field shapes plus a worked example. It still leaves 'layout' and the in-place-vs-output_path behavior of 'output_path' unexplained.

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 first sentence names a specific verb and resource (add dimensions to a DXF) and enumerates the supported kinds (linear, aligned, radius, diameter, angular) plus the fact it emits native DIMENSION entities. The only gap is differentiation from the near-identical sibling 'add_dimension', which the description never mentions or contrasts with.

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?

An explicit 'QUANDO USAR' block gives concrete triggers (dimensioning spans, distances between supports, hole diameters), which is well above implied usage. However it offers no exclusions or guidance on when to prefer a sibling such as 'add_dimension' or 'draw_line'.

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