Critical gaps across all dimensions. Tool definitions lack visible input schemas, parameter descriptions, and output documentation. No evidence of schema registration in provided source. Tool names follow verb_noun convention (list_clusters, get_context, create_cluster, create_entry) but descriptions are not visible in the code samples provided. Cannot verify parameter types, constraints, or error handling patterns. The MCP package.json shows @modelcontextprotocol/sdk dependency but actual tool registration code is not included in the source excerpt.

• Add explicit input schemas to all tools with parameter types (string, number, boolean, enum), descriptions (50-100 chars each), and constraints (min/max, regex patterns, allowed values).
• Write tool descriptions (100-200 chars) answering: What does it do? When should the LLM call it? What does it return? Example: 'list_clusters: Retrieve all available data clusters with their metadata. Call this first to discover available storage locations before creating entries.'
• Document output schemas showing all response fields, types, and whether they are required. Include pagination info (total_count, next_cursor) for list_clusters.
• Add error handling that returns actionable messages: 'Cluster not found. Available clusters: [names]. Did you mean one of these?' instead of raw error codes.
• For write operations (create_cluster, create_entry), implement a dry-run parameter or confirmation step to prevent accidental data loss.