dxf_draw

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

With no annotations, the description carries the full burden. It usefully discloses two behaviors: entities are appended (existing content is not replaced) and the file is created if absent. It says nothing about permissions, file locking, ordering, or what happens on an invalid entity type.

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 statement of purpose and creation behavior, followed by a scannable entity reference. Every line carries information that the empty schema does not, so the length is earned rather than padded.

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?

Given a mutation tool with no annotations and no output schema, the description covers the genuinely complex part (the entity dictionary grammar) completely enough to construct a valid call. Remaining gaps are path/dxfversion semantics and return behavior, which matter less than getting the entity shapes right.

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 0%, so the description must compensate, and it does so thoroughly for the hard parameter: the entity grammar, shared optional fields (layer, color with ACI/name/hex forms), and per-type required fields are all spelled out. It leaves 'path' and the 'dxfversion' default undocumented, which are minor given their obvious semantics.

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: append 2D entities to a DXF drawing, plus the create-if-missing condition. It is clearly distinguishable from read/render/export siblings, though it never explicitly contrasts itself with dxf_create or dxf_blocks, which also write geometry.

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 by 'append to a DXF drawing' and the auto-create note, but there is no explicit when-to-use versus dxf_create, dxf_blocks, or dxf_splines. The agent must infer which sibling to pick for a given geometry task.

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