Paint: Straight line

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the write/safety profile is covered. The description adds that layers, filters and undo behave identically across drawing tools, which is useful context, but it omits behavioral detail beyond that (e.g. whether re-issuing the same call stacks strokes, what preview returns).

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?

Three short sentences, front-loaded with what the tool draws and the key optional behaviors, then a shared-context note. No wasted filler, though the opening 'One segment' fragment relies on the title to be understood.

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?

With 18 parameters, no output schema and low schema description coverage, the description should carry more weight. It covers the core stroke concept and canvas/layer targeting but leaves the preview/return behavior and half the styling parameters unexplained, which is a meaningful gap for a tool this wide.

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 only 39% across 18 parameters, so the description must compensate. It clarifies dashes ([8,6] example), arrow head, hardness=0 airbrush edge, canvas-by-name and layer index, but leaves many parameters (preview, opacity, blend, cap, dash_offset, arrow_size, width) undocumented in the description as well.

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 conveys a single straight-line segment with optional dashes and arrow head, and the title reinforces it as 'Paint: Straight line'. It does not explicitly say 'draws a line', which is slightly elliptical, and it does not name the sibling it differs from (e.g. paint_path for multi-segment strokes).

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?

'For rules, grids and outlines' implies intended use cases, and 'Target the canvas by name (created with paint_canvas)' gives a precondition. However, there is no explicit when-not guidance nor any routing against near siblings like paint_path or paint_brush, so usage is only implied.

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