Server has 6 tools with basic naming and descriptions, but critical gaps in schema completeness, parameter documentation, and error handling. Tool definitions are inferred from test files and frontend code rather than explicit registration in the MCP handler. Input schemas present but lack required/optional field declarations and detailed parameter descriptions. No output schemas documented. Error handling is minimal, no recovery guidance or actionable error messages. Descriptions are present but generic (avg ~80 chars, below 194-char baseline). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite high-risk operations (delete, create, update). Security concern: approval workflow mentioned but not reflected in tool definitions or error handling.

• Add explicit tool registration in internal/mcp/handler.go with full ToolDefinition structs. Verify schema enforcement in Call() methods.
• Document output schemas for all tools. Include pagination (limit, offset, total_count) for query results. Specify field types and required fields.
• Add required/optional declarations to input schemas. Document 'records' and 'tables' array item schemas with field names, types, and constraints.
• Implement tool annotations: mark delete_records and update_records with destructiveHint=true; mark query with readOnlyHint=true; mark idempotent operations with idempotentHint=true.
• Add actionable error messages: 'Invalid base identifier. Use base name (e.g. "Contacts") or ID (e.g. "appXXX").' Include recovery guidance for common failures.

Inferred effective spec: 2025-06-18+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry