draw_spline

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

The description discloses two meaningful behavioral traits: the spline passes exactly through the given points ('through') and is smooth rather than angular. However, with no annotations, it omits potentially important behavior like layer handling, whether the spline can be closed, or error conditions for invalid point counts.

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 a single short sentence with no extraneous words. It efficiently communicates the essential function and input format without repetition.

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 tool with no annotations, zero schema coverage, and an output schema that exists, the description omits important context such as layer behavior, return values, and constraints on the points array (e.g., minimum number of points). It is barely adequate for an expert and lacks completeness for autonomous agent use.

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?

The description clarifies the structure of the 'points' parameter as an array of [x,y] pairs, which is not explained in the schema. However, the 'layer' parameter is not mentioned at all, and since schema description coverage is 0%, the description only partially compensates for parameter meaning.

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 'Smooth spline through the given points' clearly identifies the tool's output as a spline entity that passes through points, distinguishing it from siblings like draw_polyline and draw_line. The mention of 'smooth' differentiates it from a polyline, and the point format is explicit.

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 is provided on when to use this tool vs alternatives such as draw_polyline or draw_arc. There is no mention of use cases, prerequisites, or exclusions, leaving the agent without direction for tool selection.

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