Server has 5 tools with basic schemas and descriptions, but significant quality gaps. Tool names lack clear action verbs (e.g., 'scan_all_entities' is vague). Descriptions are present but inconsistent in depth, some are 1-2 lines, others embed parameter docs in the description text rather than in parameter fields. Parameter descriptions are sparse or missing entirely. No output schemas documented. Error handling returns generic strings without recovery guidance. No input validation or constraint documentation. Schemas are present but lack detail (e.g., no min/max for numeric params, no enums for color codes). Overall structure is functional but falls short of production quality.

• Rename 'scan_all_entities' to 'list_drawing_entities' or 'export_entities_to_database' to clarify the action and distinguish from read-only discovery.
• Move parameter documentation from tool docstrings into individual parameter descriptions in the schema. Each parameter (start_x, start_y, etc.) must have its own description field.
• Add output schemas for all tools. E.g., draw_line should return {handle: string, layer: string, start_point: [x, y, z], end_point: [x, y, z]} instead of a plain string.
• Add numeric constraints: start_x/start_y/end_x/end_y should have min/max bounds (e.g., -1e6 to 1e6). Radius should be > 0. Color should be an enum: {1: 'red', 2: 'yellow', 3: 'green', 4: 'cyan', 5: 'blue', 6: 'magenta'}.
• Enhance error messages with recovery guidance. E.g., 'No open document. Call create_new_drawing() first, then retry.' instead of 'No open document. Please create or open a drawing first.'