sketch_spline

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

Annotations already disclose that this is a non-read-only, non-destructive mutation. The description adds useful behavioral context: it operates on the open sketch, uses millimeter coordinates, requires at least two points, and can be closed by repeating the first point.

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?

The description is two tightly written sentences with no filler. The core action is front-loaded, followed immediately by critical input and closure semantics.

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 single-parameter sketch-entity creation tool with an output schema, the description covers the active-sketch prerequisite, coordinate format, units, minimum point count, and closure rule. Nothing essential for correct invocation is missing.

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 must carry parameter meaning. It does so fully by specifying the expected [[x, y], ...] format, units in mm, the minimum point count of 2, and the closing behavior.

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 states a specific verb and resource: drawing a smooth spline through points of the open sketch. This clearly distinguishes it from sibling sketch tools such as sketch_line, sketch_arc, and sketch_polygon.

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?

The phrase 'of the open sketch' implies the prerequisite that a sketch must be active, but there is no explicit guidance on when to use a spline over sibling tools like sketch_arc or sketch_polygon, nor any exclusions.

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