draw_line

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

No annotations are provided, so the description carries the full burden of explaining behavior. It only says a Bresenham line will be drawn; it does not disclose whether pixels are overwritten or blended, which layer is affected, how out-of-bounds coordinates are handled, or whether this mutates the file referenced by filename.

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 a single concise sentence with no wasted words, and the key functional detail ('Bresenham line') is front-loaded. However, the terseness comes at the cost of useful context, so it is concise but slightly under-specified.

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 seven parameters, no annotations, no output schema, and no parameter descriptions, the description is too sparse to fully support correct invocation. Missing details include coordinate system, target layer/file context, default color behavior, and how this differs from draw_line_at.

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 description must compensate for all seven parameters, but it only hints at thickness ('optional pixel thickness') and the line concept. It does not explain x1/y1/x2/y2 endpoint semantics, the color format, or what filename refers to beyond the schema itself.

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 clearly states the action ('Draw'), the resource ('a Bresenham line'), and the key optional behavior ('optional pixel thickness'). It is specific enough to separate this from rectangle, circle, and pixel operations, though it does not distinguish itself from the sibling draw_line_at tool.

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 about when to use this tool versus alternatives such as draw_line_at, draw_pixels, or draw_path. The description gives no context about coordinate systems, current-layer behavior, or what distinguishes this variant from the sibling drawing tools.

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