mcp-tuikit has 7 tools with complete input schemas and descriptions, but quality is uneven. Tool names follow verb_noun convention (create_session, close_session, send_keys). Descriptions are present (avg ~80 chars) but lack depth on WHEN to use each tool and what happens on failure. Parameters have types and descriptions, but lack constraints (enums, ranges, patterns). No output schemas documented. Error handling is absent, no guidance on retryability, recovery steps, or actionable error messages. The run_flow tool accepts both yaml_path and yaml_string (mutually exclusive) but this dependency is not documented. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (WRITE vs READ_ONLY). Session management tools (create_session, close_session, send_keys) lack idempotency guarantees.

• Add output schemas to all 7 tools. Document what fields create_session returns (e.g., session_id, terminal_type, dimensions), what create_snapshot returns (e.g., snapshot_id, image_url, text_content), etc.
• Add tool annotations: mark create_session, close_session, send_keys, run_flow with destructiveHint=true; mark create_snapshot, wait_for_text, check_system_dependencies with readOnlyHint=true. Include idempotentHint where applicable.
• Document run_flow parameter dependency: 'Provide either yaml_path (file path) OR yaml_string (inline YAML), not both. If both provided, yaml_string takes precedence.' Add to both parameter descriptions.
• Expand descriptions with failure modes and recovery guidance. E.g., wait_for_text: 'If timeout occurs, the pattern was not found within the window. Retry with a longer timeout_ms, or call send_keys to advance the terminal state and try again.'
• Add constraints to numeric parameters: cols/rows should have min/max (e.g., cols 20 - 200, rows 5 - 100); timeout_ms should have a range (e.g., 100 - 60000). Document in parameter descriptions.