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 behavioral disclosure, but it only states the geometric operation. It does not reveal side effects (e.g., adds entity to current drawing), default layer behavior, or any additional traits beyond the coordinates.

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 one concise, front-loaded sentence that directly conveys the tool's function with no filler or redundancy. Every word is meaningful.

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 simple drawing primitive, the description gets the core idea across, and an output schema exists so return values need not be explained. However, it omits the layer parameter, does not acknowledge default behavior (layer '0'), and offers no differentiation from similar line-drawing siblings, leaving some gaps for a tool with 5 parameters.

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 clarifies the four coordinate parameters by naming them in the context of a line from start to end, which adds meaning over the bare schema. However, the 'layer' parameter is not mentioned, and schema coverage is 0%, so the description does not fully compensate for the missing parameter documentation.

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 precisely states the tool draws a line segment defined by two endpoints (x1,y1) and (x2,y2). This is specific, uses a clear geometric resource, and naturally distinguishes from sibling tools like draw_circle or draw_polyline.

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 usage is implied: use this when you need to draw a single line segment. However, the description provides no explicit guidance on when to choose this over alternatives like draw_polyline or draw_batch, nor any exclusions or prerequisites.

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