add_line

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

With no annotations, the description must carry the transparency burden. It discloses the core effect (adds a line) and the unit system (mm), but does not mention prerequisites, failure modes, or side effects beyond the addition.

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?

One short sentence plus a parenthetical parameter clarification; every word carries meaning and the main action is front-loaded.

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 three-parameter geometric command, the description provides essential semantic details (points and units) and the target resource. It could mention needing an existing sketch or the return value, but the tool's complexity is low enough that this is a minor gap.

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 0%, so the description compensates by specifying p1 and p2 as [x, y] in mm. The sketch parameter is left to its name, but it is straightforward given the context 'to a sketch'.

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?

States a specific action ('Add'), a concrete resource ('a single line to a sketch'), and the coordinate form p1/p2. This clearly distinguishes it from sibling tools like add_rectangle, add_circle, and add_spline.

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 when-to-use or alternative guidance is provided, but the phrase 'single line' implies it is for straight segment creation rather than arcs, splines, or closed shapes. This is usable but only implicit.

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