Single tool with empty input schema ({}), minimal description lacking WHEN/WHY guidance, no parameter documentation, no output schema, and no error handling. The description is 287 chars but reads as agent instructions rather than tool documentation. Tool name 'get_ifs_development_guidance' is appropriately verb-noun, but the schema and parameter documentation are completely absent. This server fails basic definition quality standards.

• Add explicit input schema with typed parameters (even if empty, document why). If the tool truly takes no inputs, state 'This tool requires no parameters' in the description.
• Document the output schema. Specify what fields the guidance response contains (e.g., 'Returns: {guidance: string, references: [string], next_steps: [string]}'). LLMs need to know what to extract.
• Rewrite description as tool documentation: 'Provides strategic guidance on IFS Cloud architecture, development patterns, and database analysis. Use this to understand design principles before implementing features. Returns text guidance and recommended next steps.' Keep it under 200 chars.
• Expose the hybrid search engine as separate tools: 'search_ifs_documentation' (BM25S + FAISS), 'list_ifs_patterns', 'get_ifs_architecture_overview'. One guidance tool is insufficient for agent-driven research.
• Add error handling: document what happens if embeddings are not loaded (search_engine is None per code), and provide recovery guidance (e.g., 'Embeddings not available. Try get_ifs_development_guidance for strategic overview.').

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

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