line

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

No annotations are provided, so the description bears full responsibility. It names the Bresenham algorithm and explains no_doubles, but omits behaviors like default symmetry mode (implied by ignore_symmetry parameter), coordinate clipping (clip parameter), or any side effects. The transparent aspects are partial.

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?

Two concise sentences front-load the main action. No wasted words; every phrase adds value (e.g., 'Bresenham', 'no_doubles' explanation).

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?

No output schema exists, yet the description does not mention return values. Despite 12 parameters and several required ones, the description covers only the no_doubles behavioral detail. It misses context on prerequisites, coordinate system, or interaction with other tools (e.g., symmetry). Completeness is low.

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 description coverage is 58%, so baseline 3. The description adds meaning for no_doubles ('removes L-shaped double pixels for pixel-perfect diagonals'), which is absent in the schema. However, it does not explain the core parameters x1, y1, x2, y2 (endpoints) or the meaning of index (palette index). It adds some value but not fully compensating for the schema's gaps.

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 Bresenham line', specifying the verb (draw) and resource (line) with a specific algorithm. This distinguishes it from sibling drawing tools like rect, ellipse, or set_pixels.

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 explicit guidance on when to use this tool versus alternatives like set_pixels or rect. The no_doubles mention implies a use case for diagonals, but no context on when to avoid or prerequisites.

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