Teru exposes 35 tools with basic schemas and descriptions, but falls short of production quality. Most tools have 1-4 parameters with type definitions and brief descriptions (avg ~60 chars), meeting minimum viability. However, critical gaps undermine LLM usability: (1) No output schemas documented, LLMs cannot predict return structure or chain tools reliably. (2) Descriptions are generic and lack WHEN/WHY context, e.g., 'List all panes in the current workspace' does not explain when to call it vs. alternatives. (3) Parameter descriptions are minimal; many lack constraints, ranges, or format hints. (4) No error handling guidance, tools return success/failure with no recovery hints. (5) Enum constraints missing for string parameters (e.g., direction, layout, zoom direction), LLMs will hallucinate invalid values. (6) No idempotency or confirmation patterns for destructive ops (close_pane, session_restore). (7) Tool composition is weak, no chaining IDs returned in responses, forcing discovery detours. Naming is consistent (verb_noun pattern) and mostly clear, but descriptions and schemas lag production baselines.

• Document output schemas for all tools. Specify field names, types, and whether results are paginated. Example: teru_list_panes should return {panes: [{id: int, name: string, cwd: string}], total: int}.
• Add enum constraints to string parameters. Replace 'direction: string' with 'direction: enum[horizontal, vertical]'. Replace 'layout: string' with 'layout: enum[grid, tall, ...]'.
• Expand descriptions to 100-150 chars with WHEN/WHY context. Example: 'Get the current state (running/stopped/error) of a pane. Call this to check if a command completed before reading output with teru_read_output.'
• Add error handling guidance to descriptions. Example: 'If teru_wait_for times out, the pattern was not found within the line limit. Increase lines parameter or check pane_id is correct.'
• Implement confirmation pattern for destructive ops. Add optional 'confirm: bool' parameter to teru_close_pane and teruwm_close_window. Return {confirmed: false, message: 'Ready to close pane 5. Call again with confirm=true.'} on first call.