Four well-named tools with complete Zod schemas and clear descriptions. All tools are read-only with proper annotations. Naming follows verb_noun pattern (search_prompts, get_prompt, list_workflows, build_video_prompt_brief). Descriptions are substantive (100-200 chars), explaining WHAT and WHEN. Input schemas are fully typed with constraints (min/max lengths, enums, defaults). However, output schemas are not formally documented, responses are text-wrapped without explicit field definitions. Error handling is minimal (only get_prompt has try-catch). Parameter descriptions are present but could be more prescriptive about format/constraints.

• Document output schemas for all tools. Define fields, types, and nesting explicitly (e.g., search_prompts returns {items: [{slug, title, description, ...}], total, syncedAt}).
• Add error handling to search_prompts and list_workflows with actionable recovery messages (e.g., 'No results found. Try a broader query or check language filter.').
• Enhance parameter descriptions with format/constraint details: 'language: ISO 639-1 code or "all" (default). E.g., "en", "zh", "all".' and 'duration: target video length as natural language (e.g., "15 seconds", "1 minute") or ISO 8601 duration (e.g., "PT15S").'.
• Add pagination to search_prompts: include offset/limit in request, return total count and next_cursor in response. Cap default limit at 20 and enforce max 50.
• Refactor build_video_prompt_brief to return structured JSON with explicit sections (motion, camera, continuity, audio, revisionGuidance) instead of unstructured text.