draw_line

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

With no annotations, the description carries the full burden, and it does disclose two meaningful traits: Bresenham's algorithm (deterministic rasterization) and a single undo transaction (atomicity). However, it omits permissions, how layer/frame defaults are resolved, and what returnPreview changes about the response, so mutation behavior is only partially covered.

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?

A single front-loaded sentence with zero filler that still conveys the algorithm and the transactional guarantee. Nothing is redundant or buried.

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 10-parameter mutation tool with no annotations and no output schema, the description covers the core draw behavior adequately but leaves several parameters and the returnPreview behavior unexplained. It is minimally sufficient but not complete.

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?

The description only restates x1/y1/x2/y2, which the schema already documents. With 60% schema coverage, the undocumented parameters (layerName vs layerIndex, frameNumber, returnPreview) are explained in neither the schema nor the description, and no added meaning is provided for any parameter.

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 ('Draws a pixel art line') with the endpoints and algorithm named, which clearly distinguishes it from draw_rectangle, draw_ellipse, and flood_fill. It is unambiguous what the tool produces, though it does not explicitly call out sibling alternatives.

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 verb 'draws a line' but there is no explicit when-to-use guidance or comparison against related tools like set_pixels or draw_rectangle. The agent can infer the context but receives no routing help.

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