tldraw_create_line

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that the tool creates a new shape on the canvas, behaves as a mutation, or any side effects or permissions needed. For a creation tool, basic transparency about its effect is missing.

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 sentences long, with no wasted words. It front-loads the core purpose immediately and provides a key feature (interpolation types) efficiently.

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 12 parameters, no output schema, and no annotations, the description is too sparse. It does not explain the overall result (e.g., shape creation on the canvas), return value, or how parameters like parentId or rotation affect the shape. A more comprehensive description is needed for a tool with this complexity.

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 100%, meaning all parameters have individual descriptions in the input schema. The description adds only the mention of interpolation support, which is already covered by the spline parameter's description. No substantive additional meaning beyond the schema, so baseline 3 is appropriate.

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 the tool creates a line shape with multiple control points and supports straight or cubic spline interpolation. This differentiates it from other shape creation tools like tldraw_create_geo, tldraw_create_arrow, etc., by specifying the type of shape and its defining features.

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 description provides no guidance on when to use this tool versus alternatives such as tldraw_create_arrow or tldraw_create_draw. Given many sibling shape creation tools, explicit usage context would help the agent select correctly.

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