draw_line

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

No annotations exist, so the description carries the full burden; it does disclose one meaningful side effect — the layer is automatically created if missing. It does not say whether the entity is committed to the current drawing immediately, what coordinate system or units the points are interpreted in, or what happens if the connection is not established.

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 core sentence is front-loaded and the Args block is scannable with no filler. It is slightly longer than strictly needed but every line maps to a parameter an agent must supply.

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?

An output schema exists so return values need not be explained, and all four parameters are covered. However, for a drawing-mutation tool with zero annotation coverage, the absence of connection prerequisites, coordinate-system/units context, and the default-layer behavior leaves real gaps.

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 largely does: it gives accepted shapes for start_point and end_point ([x,y] or [x,y,z]), marks layer as optional with auto-creation semantics, and provides a concrete ACI color mapping (1=Red ... 7=White). Only units, coordinate system, and the default layer when omitted remain undocumented.

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 ('Draw a line') plus the host application and supported dimensionality, so an agent knows exactly what entity is created. It does not explicitly distinguish itself from draw_polyline or draw_rectangle, leaving that inference to the reader.

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?

There is no guidance on when to choose draw_line versus draw_polyline (a two-segment polyline would be equivalent), and no prerequisites such as needing an active AutoCAD connection first. Usage is only implied by the tool name.

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