draw_line

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

No annotations provided. Description only lists parameters without disclosing behavioral traits like coordinate system, whether changes are undoable, or performance implications. The description carries the full burden but is minimal.

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?

Extremely concise: single-purpose sentence followed by structured parameter list. No redundant words; every line adds value.

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 0% schema coverage, the description is too sparse. Missing coordinate system origin, color format details, thickness limits, and impact on canvas state.

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 coverage, the description adds basic semantics (e.g., 'Hex color code' for color, 'Line thickness in pixels' for thickness). However, spatial parameters (x1, y1, x2, y2) lack coordinate system explanation.

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 'Draw a line on the canvas' with specific parameters for start/end points, color, and thickness. It distinguishes from sibling tools like draw_circle or draw_rectangle.

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 vs alternatives. Does not mention when to prefer draw_line over draw_path or draw_pixels.

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