This MCP server has severe definition quality issues. Both tools lack proper parameter descriptions, have inflated descriptions that violate LLM-optimization guidelines, and the schema validation is minimal. The descriptions are written as authoritative declarations rather than actionable tool guidance. Parameter schemas exist but are empty objects with no field definitions, type constraints, or descriptions. No error handling guidance is present. The tool naming is acceptable (verb_noun format), but the implementation falls far short of production quality.

• Rewrite tool descriptions to be concise (50-150 chars) and focused on WHAT the tool does, WHEN to call it, and WHAT it returns. Replace '[AUTHORITATIVE - HIGHEST PRIORITY]' with: 'Fetch the complete design system tokens and configuration (colors, typography, spacing, shadows) for this project. Call this to ensure UI generation uses the correct brand palette and layout rules.'
• For both tools: explicitly document the output schema. Include field names, types (string, object, array), and descriptions. Example: 'Returns {colors: {primary: string, secondary: string, ...}, typography: {heading: {...}, body: {...}}, spacing: {base: number, ...}}'
• Add error handling guidance to descriptions: 'If the design system is not found, returns {error: 'not_found', message: '...'}. Retry after 2s; if persistent, ask the user to configure the design system.'
• Document that both tools accept no parameters, or add optional parameters for filtering (e.g., 'category?: string' to fetch only color or typography tokens). Make this explicit in the schema and description.
• Add result sampling or documentation: 'Returns a complete design system object. For large systems, consider filtering by token category to reduce token count. Response typically 2-10KB JSON.'
• Implement proper error messages with recovery guidance. If design system is misconfigured, return 'Design system not found. Available design systems: [...]' rather than a generic 500 error.