Two tools with minimal documentation. Tool names follow verb_noun pattern (list_, create_) but descriptions are sparse and lack actionable context. Input schemas present but parameters lack descriptions. No output schemas documented. No error handling guidance. Missing parameter constraints and validation rules. This server falls well below production baseline (median ~50).

• Expand tool descriptions to 100-200 characters. Include WHAT the tool does, WHEN to use it, and what it returns. E.g., 'Lists all Jupyter kernels available in the current environment. Call this before create_new_notebook to validate kernel names. Returns array of {name, display_name, language}.'
• Document output schemas for both tools. Specify: list_available_notebook_kernels returns {kernels: [{name: string, display_name: string, language: string}]}; create_new_notebook returns {notebook_id: string, kernel_name: string, created_at: string}.
• Add description to 'cells' parameter: 'Array of initial cells to add to the notebook. Each cell is {type: "code"|"markdown", content: string}. Optional; defaults to empty notebook.'
• Add error handling examples in descriptions: 'If kernel_name is invalid, returns error with list of available kernels. If notebook creation fails, returns error with reason (e.g., disk full, permission denied).'
• Add enum constraint to kernel_name parameter or document that it must match a name from list_available_notebook_kernels output.