Code Virtuoso defines 6 tools with partial schemas and descriptions. Most tools have descriptions (4-5 sentences), but parameter documentation is inconsistent. The annotate tool has 30+ parameters with minimal per-parameter descriptions, most lack type info beyond array/string/integer. Schemas are present but incomplete: many parameters lack descriptions, enums are missing for color/mode parameters, and output schemas are undocumented. Error handling and recovery guidance are absent. Tool names follow verb_noun convention (annotate, capture_*), which is good, but parameter naming is inconsistent (e.g., 'rect' vs 'circle' vs 'arrow' as arrays without clear coordinate semantics). No tool declares permissions, audit trails, or idempotency guarantees.

• Add per-parameter descriptions to all 30+ parameters in annotate. For color params, use enums (e.g., 'rect_color: enum [red, blue, green, yellow, black, white] or hex #RRGGBB') instead of free-form strings.
• Document output schemas for all tools. E.g., annotate should return {success: boolean, output_path: string, error?: string}. capture_* tools should return {success: boolean, output_path: string, width: integer, height: integer}.
• Standardize array parameter documentation. For annotate, clarify: 'rect: [x1, y1, x2, y2] where x1,y1 is top-left and x2,y2 is bottom-right (pixels)'. For circle, clarify: 'circle: [center_x, center_y, radius] (pixels)'.
• Add error handling guidance to tool descriptions. E.g., 'If input_image does not exist, returns {success: false, error: "File not found"}. Verify the path and retry.' This guides LLM recovery.
• Declare tool permissions and idempotency. E.g., annotate: 'Modifies output_image file (WRITE). Idempotent: same input always produces same output. Requires file write permissions.' This enables least-privilege agent configs.