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

With no annotations, the description carries the full burden and does well: it discloses that the current drawing is replaced ('in place of the current drawing'), what the call returns (counts, conversion details), and a data-loss risk (objects that cannot be read would be missing from a saved file). It omits permission/error behavior and whether the current drawing is discarded without prompt, keeping it at a 4 rather than 5.

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?

A single dense sentence, but every clause earns its place: the scope, the follow-up workflow, the return contents, and the warning about unreadable objects. Front-loaded with the core action; slightly run-on, which keeps it just under a 5.

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 summarizes the return payload (counts, conversions, warning list), which is exactly what an agent needs to interpret the result. It covers the end-to-end workflow; only error/failure handling for a missing or malformed file is left unspecified.

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 100% and the filePath description already documents path resolution and the server folder convention, so the baseline would be 3. The description adds a genuine constraint the schema lacks — the file must be ASCII DXF in the R12–2018+ range — which tells the agent what inputs are actually valid.

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+resource ('Opens an existing ASCII DXF file') and immediately disambiguates the operation with 'in place of the current drawing', which separates it from cad_new_drawing and the export siblings. An agent can tell exactly what this does without opening the schema.

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?

Names the downstream tools and the intended workflow ('edited with cad_run_commands and saved with cad_export_dxf'), which gives clear context for when to reach for it. It stops short of explicit exclusions (e.g. when to prefer cad_open_shared or cad_new_drawing instead), so it is strong context rather than full when/when-not guidance.

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