Shun exposes 58 tools with minimal schema documentation and sparse descriptions. Most tools lack parameter type definitions, descriptions are generic (10-50 chars), and output schemas are undocumented. Shell tools (bash, run) accept command strings with no validation guidance. GitHub/Figma/Gmail/Cloudflare tools have one-line descriptions that don't explain WHEN to use them or what they return. No error handling guidance, no recovery paths, no permission scopes declared. Tool names are inconsistent (github_pr_read vs github_issue_list mixing underscores). Many tools appear inferred from code rather than explicitly registered with full schemas. This is a desktop harness, not a production MCP server.

• Add full JSON Schema input definitions to all 58 tools. Include type, description, enum constraints, and min/max bounds for every parameter. Currently only bash/run have partial schemas.
• Expand tool descriptions from 1-2 sentences to 50-150 chars explaining: what the tool does, when to use it vs similar tools, and what data it returns. Reference pattern:tool-description.
• Document output schemas for all tools. Specify which fields are returned, their types, and which IDs/references are needed for chaining to downstream tools.
• Add error handling guidance: categorize errors as retryable/user-fixable/fatal, include the invalid value and constraint violated, and suggest recovery steps (e.g., 'User not found. Try search_users() first.').
• Implement confirmation/dry-run patterns for destructive tools (delete, send, publish). Return a confirmation_required response with a confirm_action tool to prevent accidental data loss.