TomoriBot is not an MCP server, it is a Discord bot with a custom tool system. Tool definitions exist only as string constants in toolNotices.ts with no visible input schemas, parameter descriptions, or output documentation. No tool registration mechanism, no JSON Schema, no error handling patterns. The 13 tools are listed by name and brief description only, with no structured metadata. This fails the fundamental requirement that MCP tools must have complete, machine-readable schemas.

• Create a formal tool registry with JSON Schema for each tool. Define input parameters with type, required flag, description, and constraints (enums, min/max, patterns).
• Expand tool descriptions to 50 - 200 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and WHAT it returns. Example: 'Search the web for current information. Use when you need recent news, facts, or URLs. Returns a list of results with title, URL, and snippet.'
• Document output schemas. For each tool, specify the response structure: field names, types, and what each field means. Example: web_search returns [{title: string, url: string, snippet: string, date: ISO8601}].
• Add parameter descriptions and constraints. For search tools, document query length limits, result count limits, and supported filters. For generation tools, document prompt length, style options, and output formats.
• Implement error handling patterns. Document which errors are retryable (network timeout, rate limit) vs user-fixable (invalid query) vs fatal (API key invalid). Provide recovery guidance in error messages.