dxf_blocks

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 that the file is auto-created when missing and that a duplicate block name raises an error, which is genuine behavioral context. It does not cover permissions, what happens to pre-existing drawing content, or return behavior.

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 purpose is front-loaded in the first clause, followed by a well-structured indented list of nested fields. It is appropriately sized for a nested-object tool, with only minor redundancy across the layer/color 'common optional fields' note.

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 no annotations, no output schema, and nested objects, the description supplies the crucial nested-entity contract and the duplicate-name/auto-create behaviors. It is slightly short on top-level parameter semantics (path, dxfversion) and any return/confirmation behavior.

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% and the schema only declares opaque arrays (additionalProperties: true), so the description's detailed breakdown of blocks (name/base_point/entities) and refs (block/insert/rotation/x_scale/y_scale/layer/color) is a substantial compensation. It omits the required path and the dxfversion parameter, but documents the nested contract the schema leaves blank.

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 pair of verbs and resources: define blocks (BLOCK) and insert block references (INSERT), plus an auto-create side effect. It references the sibling dxf_draw to anchor the entity format, though it doesn't fully spell out its role distinction from dxf_create or dxf_draw.

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 the operation (use this when you need reusable block definitions plus inserts), and it notes that the block entity format matches dxf_draw. There is no explicit when-to-use-vs-alternatives or when-not guidance, so the agent must infer the boundary with dxf_draw/dxf_create.

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