Four tools with complete input schemas and descriptions. Tool names follow verb_noun pattern (build_, plan_, diagnose_, get_). Schemas are well-structured with type constraints, enums, and min/max bounds. Descriptions are substantive (100-200 chars). However, output schemas are not documented in the source code, LLMs cannot see what fields to expect from responses. Error handling is absent; no recovery guidance or actionable error messages. Parameters are well-constrained but lack dependency documentation (e.g., referenceBindings interaction with workflow). No tool annotations beyond toolAnnotations=true flag.

• Document output schemas for all four tools. For build_motion_prompt, specify: {workflow, outputLanguage, idea, durationSeconds, aspectRatio, subjectMotion, cameraMotion, lighting, visualTreatment, referenceBindings, constraints[], prompt, revisionMoves[]}. For plan_reference_sequence, specify: {idea, shotCount, totalDurationSeconds, referenceBindings, continuityAnchor, cameraStyle, shots[{shot, timing, purpose, direction, camera, continuity, endFrame}], assemblyNote}.
• Add error handling descriptions. E.g., 'Returns error if idea is empty or exceeds 5000 chars. Returns error if durationSeconds is outside 1-120 range. Errors are retryable, adjust parameters and retry.'
• Document parameter relationships. E.g., 'referenceBindings and avoid are optional but recommended when workflow is reference-to-video or video-to-video. If both are provided, referenceBindings takes precedence in conflict resolution.'
• Explicitly state idempotency. Add to tool descriptions: 'This tool is deterministic, identical inputs always produce identical outputs. Safe to retry without side effects.'
• Enhance get_oxvodo_resources description. Specify: 'Returns a structured object with topic-specific resources. For topic=prompting, returns {tips[], examples[], constraints[]}. For topic=workflows, returns {workflows[{name, description, steps[]}]}. For topic=all, returns all categories merged.'