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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write/network profile is covered. The description adds genuinely useful behavior beyond that: closed outlines become editable extrude nodes, and the response reports declared units and unread entity types.

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 verb and resource, and each sentence carries information (parametric behavior, editable nodes, response contents). Slightly dense with three long clauses in the middle, but nothing is wasted.

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 compensates by describing what the response reports (declared units, unread entity types). Combined with full schema coverage and annotations covering safety, the definition is sufficient for correct invocation.

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 description coverage is 100% across all six parameters, so the schema already documents url, base64, ticketId, height and unitFactor including the create_upload routing and the 6 MB limit. The description's unit-reporting sentence reinforces unitFactor's role but adds no new parameter syntax. Baseline 3 applies.

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 ('Import a DXF as a new project, extruded into solid geometry') and immediately differentiates itself from the sibling import_model by contrasting parametric vs mesh behavior. An agent can select it correctly 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?

The contrast with mesh import ('Unlike a mesh import this stays PARAMETRIC') gives clear context for when this tool is the right choice. However it stops short of explicitly naming import_model as the alternative or stating exclusions, leaving the routing to inference.

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