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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the entity mapping (points to POINT, lines and polygon rings to LWPOLYLINE) and the layer handling (properties.layer to group code 8, default '0'). However, it does not mention behavior for MultiPolygon, GeometryCollection, or coordinate system handling, which are common edge cases.

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?

The description is three sentences long, front-loaded with the primary purpose, followed by the entity mapping and layer behavior. Every sentence adds value, with no filler or repetition.

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?

The description covers the essential conversion logic and layer handling, making the tool's behavior clear. It does not address unsupported geometry types or coordinate reference system considerations, but the presence of an output schema covers return values. For a single-input conversion tool, this is reasonably complete.

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?

The input schema has zero description coverage, so the description must compensate. It clarifies that the 'geojson' parameter is the GeoJSON data to be converted, which adds a little meaning beyond the bare schema. However, it does not specify expected format details (e.g., raw string vs. file path, CRS expectations), leaving gaps for a 0% coverage situation.

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 description clearly states the tool converts GeoJSON to an AutoCAD DXF file, using specific verbs and resources. It distinguishes itself from sibling tools like dxf_to_geojson (reverse direction) and includes user-phrase examples to reinforce the intended use.

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 provides examples of when to use the tool (e.g., 'export this GeoJSON to DXF for AutoCAD', 'convert to .dxf for Civil 3D'), which clearly indicate the context. It does not explicitly mention alternatives or exclusions, but the naming and examples make the appropriate scenario obvious.

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