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

Annotations already declare write/openWorld/non-idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond them: the result is parametric (each closed outline becomes an editable `extrude` node) and the response reports declared units and unread entity types — meaningful disclosure for a tool with no output schema.

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?

Three sentences, front-loaded with the action and result, and each sentence carries information. The rhetorical aside ('a drawing someone sent you becomes a model you can change') is slightly verbose but still clarifies the parametric payoff.

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?

For a mutation tool with annotations covering safety and no output schema, the description supplies the parametric behavior and the key return contents (declared units, unread entity types). It omits failure behavior and size limits, but those are largely covered in the schema.

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% with 6 well-documented parameters, so the schema carries parameter meaning. The description only indirectly touches semantics by mentioning the reported unit, which relates to unitFactor, adding little beyond the schema's own guidance.

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+outcome: import a DXF as a new project extruded into solid geometry, and explicitly contrasts with mesh import to distinguish it from the sibling import_model. An agent can tell exactly what this produces without reading 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?

The contrast with mesh import gives clear selection context (parametric vs. static geometry), and the schema steers callers with on-disk files to create_upload. However, no sibling is named directly and there is no explicit when-not guidance beyond the mesh contrast.

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