Server has 13 tools with basic schemas and descriptions, but significant gaps prevent production use. 4 tools (update_pilot, update_event, update_car, record_qualification_run) lack visible descriptions entirely, automatic 0 on description dimension. Parameter descriptions are sparse or missing across most tools. Output schemas are undocumented. Error handling is minimal (generic catch-all in index.ts). No tool annotations (readOnlyHint/destructiveHint). Naming is verb-first and clear, but parameter naming lacks type suffixes (e.g., 'pilotId' vs 'pilot_id'). No pagination support on query_database despite accepting arbitrary Prisma queries. Destructive tools (delete_*) have no confirmation or dry-run pattern.

• Add descriptions to update_pilot, update_event, update_car, and record_qualification_run. Each should state WHAT it modifies, WHEN to use it, and any prerequisites (e.g., 'Updates an existing pilot's profile. Requires pilot ID. Modifies state, not idempotent if called twice with different values.').
• Add parameter descriptions to all tools. For each parameter, explain what it controls, valid range/format, and any dependencies. Example: 'pilotId (number, required): The unique identifier of the pilot to update. Must exist in the system.'
• Document output schemas for all tools. Specify which fields are returned, their types, and which are safe to pass to downstream tools. Example: 'Returns {id: number, firstName: string, cars: [{id, make, model}]}'.
• Implement pagination on query_database: add limit (default 20, max 100) and offset parameters. Return {results: [...], total: number, hasMore: boolean} to prevent context window exhaustion.
• Add tool annotations: mark delete_* tools with destructiveHint=true, mark get_* and query_database with readOnlyHint=true, mark create_* with idempotentHint=false. This helps agents reason about side effects.