create_line

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the creation action. It does not mention side effects, canvas interaction, or any non-obvious behavior like whether it adds a new element or modifies existing ones.

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 sentence and is concise, but it is too under-specified to be considered appropriately sized for an 8-parameter tool. It earns its place for purpose clarity but omits essential guidance.

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?

Given the tool's complexity (8 optional parameters, no annotations, no output schema), the description is severely incomplete. It provides no context about defaults, rendering, or how the line appears, making it insufficient for an agent to use correctly.

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?

All 8 parameters have no schema descriptions (0% coverage), and the description does not compensate by explaining any parameter meanings or relationships. The word 'horizontal' implies the line's orientation but gives no insight into x, y, width, stroke, etc.

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's function with a specific verb ('Create') and resource ('horizontal divider line'), which differentiates it from sibling tools like create_rectangle or create_text. It conveys the exact purpose without ambiguity.

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 usage guidance is provided—the description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or context. A clear gap for a creation tool among many sibling creation tools.

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