Create Drawing

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

No annotations are provided, so the description carries the full disclosure burden. It clearly says the operation creates a file, but it does not disclose overwrite behavior, handling of existing files, file-system side effects, or any other consequences. For a file-creation tool this is a notable gap.

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 compact and front-loaded: a single purpose sentence followed by concise parameter bullets. There is no filler or redundancy, and every line contributes usable information.

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?

This is minimally viable for a simple creation tool: an agent can understand the main action and most parameters, and an output schema exists. Still, the required file_path is undocumented in both the description and schema, and the absence of overwrite/side-effect context leaves an important gap.

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?

With 0% schema description coverage, the bullet examples add real value for dxf_version, units, and layers. However, the required file_path parameter is completely omitted, so its semantics must be inferred from the schema field name.

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 states a specific verb and resource: 'Create a new blank DXF CAD drawing file.' The word 'blank' also differentiates this from sibling tools that read, query, export, or add content to existing drawings.

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 only implied: this tool is for creating a fresh, empty drawing. There is no explicit guidance about when to prefer it over alternatives such as add_entities or execute_ezdxf_script, nor any when-not-to-use conditions.

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