tldraw_create_draw

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

With no annotations, the description must cover behavior. It adds detail about automatic point encoding, but does not mention side effects, permissions, or that the shape is a path. For a create tool, this is adequate but not comprehensive.

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 with 17 words, front-loading the purpose and key input. No superfluous information.

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 13 parameters, many sibling tools, and no output schema, the description is too minimal. It lacks context about when to use this vs. other creators, what the return value is, and how to handle edge cases (e.g., empty points array).

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 coverage is 100%, so baseline is 3. The description does not add meaning beyond the schema for individual parameters (the encoding detail is a general behavior, not per-parameter).

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 freehand drawing shape from points, distinguishing it from other shape creation tools (geo, text, arrow, etc.) by specifying 'freehand drawing' and mentioning automatic encoding of points.

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 implies usage for freehand strokes but does not explicitly contrast with sibling creation tools (e.g., use this for organic shapes vs. tldraw_create_geo for geometric shapes). No when-not-to-use or alternative guidance is provided.

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