PCB Lens defines 6 tools with clear domain focus (IPC-2581 PCB analysis). Tool names follow verb_noun pattern (get_*, export_*) and are appropriately specific. Descriptions are present and domain-appropriate (avg ~120 chars), exceeding the 20-char minimum. Input schemas are visible with type declarations. However, output schemas are not documented in the provided code, parameter descriptions lack detail on formats/constraints, and error handling guidance is minimal. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Missing pagination guidance for potentially large results (e.g., get_pcb_net). Composition is sound, each tool has one responsibility and tools chain naturally (export → query). Security posture is reasonable (read-only operations, file-based I/O) but no explicit validation or error recovery patterns visible.

• Document output schemas for all 6 tools. Include field names, types, and descriptions. Example: get_pcb_metadata returns {layers: [{name, thickness_um, material}], board_size_um: {width, height}, ...}.
• Enhance parameter descriptions with format constraints. E.g., 'refdes: exact component reference (case-sensitive, e.g. U5, C10, R22)' and 'net_name_pattern: regex pattern (case-sensitive, anchors supported, returns first 100 matches)'.
• Add tool annotations: readOnlyHint=true for all get_* and export_* tools; destructiveHint=true for export_* tools that write files (to signal side effects).
• Add error handling guidance in tool descriptions. E.g., 'Returns {error: "file_not_found"} if IPC-2581 file does not exist, check path. Returns {error: "no_matches"} if regex matches no nets, try a broader pattern.'
• Add pagination to get_pcb_net: accept optional limit (default 100, max 1000) and offset parameters; return total_count and has_more in response.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry