figma_create_line

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

With no annotations provided, the description must carry the full burden of behavioral disclosure, but it only says 'Create a line.' It does not describe coordinate space, units, default properties, or how the line is placed in the document.

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?

'Create a line.' is extremely concise, but this is under-specification rather than efficient communication. It front-loads the core action but omits essential details, failing to earn its place as a useful tool description.

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 8 parameters, no output schema, and no annotations, a one-sentence description is severely incomplete. It does not explain return values, side effects, or how this tool fits into the broader Figma workflow.

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 only 13%, and the description adds nothing about parameter meanings. While some property names are self-explanatory (startX, startY, endX, endY), fields like parentId, name, strokeColor, and strokeWeight lack explanation beyond the raw schema.

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 'Create a line.' clearly states the action (create) and the resource (line), distinguishing it from sibling create tools for ellipses, rectangles, and text. However, it lacks any context about the Figma canvas or coordinate system, making it less informative than it could be.

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 gives no guidance on when to use this tool versus alternatives like create_path or create_from_svg. It does not mention prerequisites such as a parent container or how this differs from drawing a path with multiple segments.

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