draw_line_in_sketch

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

No annotations are provided, so the description carries the full burden of disclosure. It fails to mention behavioral traits such as whether existing sketch entities are modified, coordinate system assumptions, or side effects. The agent has no information on what happens when the tool is invoked.

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 extremely short but under-specified; it is not concise in a helpful way. Every sentence should provide value, but here the single sentence adds none, making it insufficient for the tool's complexity.

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?

With 5 parameters, no output schema, and 47 sibling tools, the description is woefully incomplete. It lacks information on return values, error conditions, sketch activation requirements, coordinate system, or relationship to geometric constraints.

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% with minimal parameter descriptions ('Body name', 'Start X', etc.), but the tool description adds no additional meaning. It does not clarify units, whether coordinates are absolute or relative, or the expected format for string inputs (e.g., expressions). Baseline is 3 due to high coverage, but the description adds zero value.

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 'FreeCAD tool: draw_line_in_sketch' is purely tautological, restating the tool name without explaining what the tool does. It does not specify that it draws a line segment in a sketch, nor does it differentiate from drawing tools like draw_circle_in_sketch or draw_rectangle_in_sketch.

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 guidance is provided on when to use this tool versus alternatives such as draw_rectangle_in_sketch or adding constraints. There is no mention of prerequisites (e.g., an active sketch) or context for when a line is appropriate.

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