create_line

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

No annotations provided, so the description carries full burden. It discloses return value (geometry with endpoints and length) and includes a critical caveat about the line not being parametric (modify_dimension cannot adjust endpoints or length). This reveals important behavioral limits beyond the simple 'draw' action.

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 first sentence front-loads the purpose. The structure includes args, return, usage, and caveats. The bilingual caveat adds length but is reasonable for international users. Could be slightly more concise, but overall well-organized.

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?

Despite no output schema or annotations, the description covers purpose, parameters, return value, prerequisite, and an important behavioral caveat. It does not mention whether the line is immediately visible or if there are constraints, but this is sufficient for a simple tool given sibling context.

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 0%, so the description must add meaning. It explains x1_mm, y1_mm as 'Start point in mm (sketch-local frame)' and x2_mm, y2_mm as 'End point.' This provides units and frame context that the schema lacks, though coordinate system orientation or bounds are omitted.

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 'Draw a line on the active sketch.' It distinguishes the tool from siblings like create_rectangle, create_circle, and create_arc by noting it is used for non-rectangular profiles before extrusion. The verb 'Draw' and resource 'line' are specific.

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 explicitly requires an active sketch via 'requires an active sketch (call create_sketch first).' It also implies usage as a building block for non-rectangular profiles, but does not explicitly exclude alternatives (e.g., use create_rectangle for rectangles). Clear context but lacks explicit exclusions.

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