Both tools lack critical definition quality. metadata_retrieve has NO input schema despite docstring mentioning a 'query' parameter that doesn't exist in the actual signature, a dangerous mismatch. entity_retrieve has a minimal schema with only 'query' string, no description of what the query should contain or expected output format. Descriptions are present but generic (194 chars baseline; these are ~150 chars). No output schemas documented. No error handling guidance. No parameter constraints (enums, ranges). Tool names use verb_noun pattern correctly but lack clarity on what 'retrieve' returns. Both tools return unstructured strings instead of structured JSON, violating response-shaper pattern.

• Add explicit input schema to metadata_retrieve: remove the 'query' parameter from docstring or add it to the function signature with type and description. Currently the docstring and code are contradictory.
• Convert both tools to return structured JSON objects instead of strings. metadata_retrieve should return {items: [{id, name, author, modified, ...}], total: N}. entity_retrieve should return {entities: [{id, label, relationships: [...]}], query_score: 0.85}.
• Document output schemas in tool descriptions. E.g. 'Returns a JSON object with fields: entities (array of {id, label, score}), total_found (int), query_embedding_used (bool).'
• Add parameter descriptions and constraints. For entity_retrieve query: 'Natural language search query (10-500 chars). Examples: "financial reports 2024", "customer complaints". Semantic similarity threshold: 0.75 (configurable via top_k parameter, default 5).'
• Implement error handling with recovery guidance. Catch connection errors and return: {error: 'Neo4j unavailable', retry_after_seconds: 30, fallback: 'Try entity_retrieve with a simpler query or check system status.'}.

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

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