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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces this with 'Only reads the model; returns download links.' It also adds genuine behavioral context beyond annotations: cut coordinate conventions in metres, the default cut when none is supplied, the effect of cutsAtSupports, and the max3dMegabytes skip behavior.

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 purpose and the two output types, then the cut syntax, then the read-only/download-link note. It is dense and long, but for a 17-parameter tool nearly every clause carries distinct information; a few items (e.g. drawings2d, name) are left to the schema rather than repeated.

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?

With 17 parameters and no output schema, the description does the important work: it explains the cuts structure, default and support-cut behavior, the 2D/3D outputs, and that results come back as download links. Some parameters (drawings2d, name, wireframe interplay) are left entirely to the schema, but nothing an agent needs to call it correctly is missing.

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 82%, so the baseline is 3, but the description meaningfully extends semantics for the undocumented 'cuts' array: kinds (cross/long/level) with their reference frames, 'at' in metres, and 'depth' meaning how far beyond the cut to draw. It also clarifies units labeling (m/ft for levels and chainages) beyond the schema's own enum description.

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: draws the open CIVIL NX model as DXF, producing both a 2D drawing (DXF 2000, with plan/elevation/iso/cuts/sections) and a 3D polyface-mesh DXF. It explicitly ties itself to the Model to IFC plugin's drawing engine, which separates it from siblings like model_to_ifc (IFC export) and dxf_import (opposite direction).

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?

Usage is implied rather than spelled out: the tool reads the model and returns download links, and cut defaults ('none given = one across mid-span, cutsAtSupports adds one at each pier') give context on how it behaves by default. However, there is no explicit statement of when to choose this vs model_to_ifc, model_report_export, or dxf_inspect, and no prerequisites or exclusions are named.

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