13 tools with mostly complete schemas and descriptions, but significant gaps in parameter documentation and error handling. Tool names follow verb_noun convention (get_, merge_, build_, run_). Descriptions present but generic (avg ~60 chars, below 194-char baseline). Most tools lack parameter descriptions beyond titles. No error recovery guidance. Tool 13 (run-script) has NO visible input schema. Composition is reasonable, tools chain via JSON inputs, but parameter naming inconsistencies (set_number vs set_list_id) and missing validation rules reduce clarity.

• Add explicit input schema to run-script with parameter descriptions and examples. Document what BricksScript syntax is accepted and what errors can occur.
• Expand parameter descriptions to include format constraints, valid ranges, and examples. E.g., 'set_number (string, format: XXXXX-Y, e.g. 75192-1, required): The Rebrickable set identifier.'
• Document output schemas for all tools. E.g., get-set-overview returns {set_num, name, year, num_parts, theme_id, ...}. Include field types and whether fields are always present.
• Add error handling guidance: 'If set_number is invalid, the API returns 404. Try search_sets() with a partial name.' Include HTTP status codes and recovery paths.
• For JSON-accepting parameters (merge-collections, build), provide a JSON schema or example showing required/optional fields. Validate input early and return 'Invalid collection JSON: missing required field "parts"' rather than a generic error.