Server has 37 tools with significant quality gaps. Most tools lack input parameter schemas (only 2 of 37 have visible schemas: get_node_info and get_nodes_info). Descriptions are present but generic (avg ~50 chars, well below 194-char baseline). No output schemas documented. Parameter descriptions missing entirely for most tools. Error handling is minimal, tools return raw JSON or generic error strings without recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Composition is reasonable (verb_noun naming, single responsibility), but schema and parameter documentation are critically deficient.

• Add Zod schemas to ALL 35 tools missing them. Example: create_frame should have {x: z.number(), y: z.number(), width: z.number(), height: z.number(), name: z.string().optional(), parentId: z.string().optional()}.
• Expand descriptions to 50-200 chars with WHAT, WHEN, and WHAT-IT-RETURNS. E.g., 'Create a new frame at (x,y) with given dimensions. Use this to group related elements. Returns frame ID and bounds.'
• Add tool annotations: mark delete_* tools with destructiveHint=true, read-only tools with readOnlyHint=true, idempotent tools with idempotentHint=true.
• Document output schemas for all tools. E.g., get_node_info returns {id: string, name: string, type: string, x: number, y: number, width: number, height: number, ...}.
• Enhance error handling: catch errors, classify as retryable/user-fixable/fatal, and return actionable messages. E.g., 'Node not found (nodeId=abc123). Try scan_nodes_by_types() to find available nodes.' instead of generic error.