Server has 4 tools with basic schemas and minimal descriptions. All tools have input schemas with proper JSON Schema structure and type definitions. However, descriptions are extremely terse (10-35 chars), parameter descriptions are completely absent, and output schemas are undocumented. No error handling guidance, no parameter constraints (enums, ranges), and no indication of idempotency or side effects. Naming is verb-first and clear (list_, create_, get_, put_), but parameter documentation is missing entirely. This is a typical community server with functional definitions but insufficient LLM-optimization.

• Expand all tool descriptions to 50 - 150 characters. Example: 'list_custom_modes' → 'List all custom modes defined in .roomodes. Returns an array of mode objects with slug, name, roleDefinition, customInstructions, and groups. Call this first to discover available modes.'
• Add descriptions to every parameter. Example: 'slug: A unique, URL-safe identifier for the custom mode (lowercase alphanumeric and hyphens, 3 - 50 chars). Used as the key in .roomodes and in get/put operations.'
• Document output schemas in tool descriptions. Example: 'Returns a JSON object with fields: slug (string), name (string), roleDefinition (string), customInstructions (string), groups (array of strings).'
• Add error recovery guidance. Example: 'If slug not found, call list_custom_modes to see available modes, or check the .roomodes file path.'
• Declare side effects and idempotency. Example: 'create_custom_mode: Creates a new mode and writes to .roomodes. Not idempotent, calling twice with the same slug will append a duplicate. Use get_custom_mode_fields + put_custom_mode_fields to update an existing mode.'