Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. run_tests and type_check both lack descriptions for their input parameters (testFiles and files respectively). Schemas are present but minimal, no enums, ranges, or validation hints. Output is unstructured text rather than typed objects. Error handling returns text but lacks recovery guidance. No tool annotations (readOnlyHint, idempotentHint). Naming is acceptable (verb_noun pattern) but descriptions are generic and under 200 chars. This server falls into the 'fair' range with noticeable gaps typical of community implementations.

• Add descriptions to all input parameters. For 'testFiles': 'Optional test file path or array of paths to run. If omitted, runs all tests. Paths are relative to the project directory.' For 'files': 'Optional file path or array of paths to type check. If omitted, checks all TypeScript files in the project.'
• Return structured output objects instead of plain text. For run_tests, return {passed: number, failed: number, skipped: number, tests: [{name, path, status, duration}]}. For type_check, return {errorCount: number, errors: [{file, line, column, message}]}.
• Add tool annotations. Mark both tools with readOnlyHint: true and idempotentHint: true since they do not modify state and can be safely retried.
• Enhance error messages with recovery guidance. Instead of 'Invalid arguments for run_tests: ...', return 'Invalid test file path. Provide a path relative to the project directory, or omit to run all tests.'
• Add input constraints to parameter descriptions. Specify that file paths must be relative to the project root, and that arrays must contain at least one element if provided.