draw_line

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

The description adds some behavioral context by mentioning 'Uses native Aseprite brush when > 1' for thickness, which is beyond the schema. However, it lacks disclosure about destructive nature, undo, coordinate system, or effects on existing content. With no annotations, the burden is higher.

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?

Single sentence, no redundancy, front-loaded action and key parameters. Efficient for its purpose.

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?

Given no output schema and no annotations, the description is too brief. It does not explain coordinate system, what happens if layer/frame is missing, or return value. For a tool with 10 parameters, more context is needed.

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 coverage is 100% with clear descriptions for all parameters. The only additional value from the description is the note about brush behavior for thickness > 1. Baseline 3 is appropriate given high schema coverage.

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) and resource (line between two points on a specific layer and frame). It effectively distinguishes from siblings like draw_rect or draw_circle by specifying 'line between two points'.

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?

No guidance on when to use this tool versus alternatives like draw_pixels or draw_rect. No prerequisites, exclusions, or context about layer/frame existence provided.

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