Preflight is a demo/testing harness for MCP servers, not a production tool server itself. The 14 bundled demo tools have complete schemas and descriptions, but quality varies. Most tools follow verb_noun naming (list_tickets, get_customer, create_ticket). Descriptions are present and adequate (50-200 chars typical). Schemas include proper types and enums. However, tool #9 (ambiguous_operation) lacks a description entirely, and several tools lack parameter descriptions. Error handling is minimal, no recovery guidance or actionable error messages visible in schemas. The server demonstrates good schema structure but lacks production-grade error handling and some parameter documentation.

• Add a description to ambiguous_operation explaining what it does, when to use it, and what it returns. Current state makes it unusable.
• Document output schemas for all tools. Include field names, types, and which fields are required. Example: 'Returns {ticket_id: string, status: string, created_at: ISO8601}'.
• Add error handling guidance to tool descriptions. Example: 'If customer_id not found, returns 404 with available customer IDs. Retryable: no.'
• Add dry_run or confirm parameters to delete_project and revoke_api_key to prevent accidental destructive operations by agents.
• Expand parameter descriptions to include constraints. Example: 'limit: Maximum tickets to return (1-50, default 20)' instead of just 'Maximum number of tickets to return.'