draw_line

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

With no annotations, the description carries the full burden of disclosing behavior, but it only states the geometric operation. It does not mention that this modifies the active drawing, how the optional layer parameter behaves, or what side effects or errors may occur.

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 extremely concise, containing no filler words and front-loading the core concept. It is a fragment rather than a full sentence, but for a simple line-drawing primitive the brevity is acceptable.

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?

The description covers the essential line-drawing semantics and the output schema exists, so return values do not need explanation. However, it omits the meaning of the `layer` parameter and the requirement of an active drawing context, leaving the tool minimally viable but with clear 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?

The phrase 'from (x1, y1) to (x2, y2)' adds meaning to four of the five parameters, clarifying that they are endpoint coordinates. However, the optional `layer` parameter receives no explanation, and the schema property descriptions are entirely absent (0% coverage), so the description only partially compensates for the missing schema detail.

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 that the tool creates a line from (x1, y1) to (x2, y2), which clearly identifies the resource and distinguishes it from sibling tools like draw_circle, draw_rectangle, or draw_text. However, it lacks an explicit verb like 'draw' or 'create' in the description itself, relying on the tool name to carry the action.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites such as an active drawing. There are no exclusions or alternative tool references, so the agent gets no contextual selection help.

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