create_line

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

Discloses return value (geometry endpoints+length), non-parametric nature of sketch, and that modify_dimension only affects extrusion depth. No annotations provided so description carries full burden; could mention if line can be edited by other means.

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?

Well-structured with purpose, args, return, usage, caveats. However, includes redundant bilingual text (Spanish and English) for the same caveat, making it longer than necessary.

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?

Covers prerequisites (active sketch), return value (geometry), param semantics, and key limitation (non-parametric). No output schema but return described. Sufficient for a simple line tool.

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?

0% schema coverage, so description compensates by explaining x1_mm/y1_mm as start point, x2_mm/y2_mm as end point, units in mm, and sketch-local frame. Adds meaningful context beyond 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?

Clear verb 'Draw' and resource 'line on active sketch'. Distinguishes from sibling tools like create_rectangle, create_arc by specifying it's for lines.

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?

Explicitly states prerequisite (active sketch via create_sketch), use case (building block for non-rectangular profiles before extrusion), and limitation (not parametric, must rebuild for resizing). Provides alternative action.

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