Six tools with complete input schemas and descriptions, but quality is uneven. All tools are READ_ONLY (good for safety), but descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool vs. alternatives. Parameters lack constraints (enums, ranges, formats). Output schemas are not documented, LLMs cannot plan downstream calls. No error handling guidance. Tool names follow verb_noun convention but lack specificity (e.g., 'consult_before_change' is vague about what 'consult' returns). Average description length ~80 chars (below 194-char baseline for A+ tools). No parameter descriptions beyond the property name itself.

• Add output schemas to all tool definitions. Document the structure of DesignGuidance, ValidationResult, ComponentSuggestion, etc. in the tool's inputSchema or a separate outputSchema field. Include field types, required fields, and examples.
• Expand parameter descriptions to 50 - 150 chars each. For 'intent', write: 'Natural language description of the frontend change you plan (e.g., "Add a dark mode toggle to the header"). Used to match against existing patterns and design guidelines.' For 'styles', write: 'CSS-in-JS object or Tailwind class string to validate against the design system (e.g., {color: "#FF5733", padding: "16px"}).'
• Convert description lists to enums. Change get_current_patterns 'category' from a string with description 'Optional category filter (components, colors, spacing, typography)' to an enum: {type: 'string', enum: ['components', 'colors', 'spacing', 'typography'], description: 'Filter patterns by category. Omit to return all categories.'}
• Disambiguate overlapping tools in descriptions. Add to consult_before_change: 'Call this BEFORE writing code to get design guidance. Use validate_proposed_code AFTER writing code to check compliance.' Add to validate_proposed_code: 'Call this AFTER writing code to validate against the design system. Use consult_before_change BEFORE writing to get guidance.'
• Add error handling guidance to all tools. E.g., 'If the design system is not loaded, returns {error: "Design system not initialized. Run guru init in the project root."}. If a file path is invalid, returns {error: "File not found: <path>. Check the path and try again."}'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry