Server exposes 4 tools with mixed quality. connection_status has a proper empty schema and clear description. search and fetch are ChatGPT-compat meta-tools with descriptions but NO visible input schemas in the provided code, only inferred from chatgpt-compat.ts reference. submit_feedback has a description but schema not visible. Tool naming follows verb patterns (search, fetch, submit). Descriptions are present but vary in detail. Overall definition quality is hampered by incomplete schema visibility and lack of parameter-level documentation.

• Add complete input schemas for search and fetch tools. Include type, description, and constraints for every parameter (e.g., query: string, limit: integer 1-100, offset: integer >= 0).
• Expand tool descriptions to 80-150 characters. Example for search: 'Search Whop API operations by keyword or category. Returns operation names, descriptions, and required parameters. Use before fetch to discover available actions.'
• Document output schemas for all tools. Specify returned fields, types, and whether results are paginated. Example: 'Returns {operations: [{name, description, params}], total_count, next_cursor}'.
• Add parameter descriptions to connection_status (if any params added) and clarify what 'permission profile' and 'tool coverage' mean in the response.
• For fetch tool, implement and document a dry-run mode or confirmation token flow (already referenced in code as MCP_CONFIRMATION_TOKEN_FIELD) to gate destructive operations.