CData Connect Cloud MCP server demonstrates solid tool design with consistent naming patterns (verb_noun: queryData, execData, getCatalogs, etc.) and comprehensive parameter schemas using Zod. All 12 tools have descriptions and input schemas. However, descriptions are brief (avg ~80 chars, below the 194-char baseline for A+ tools), lack dependency hints and recovery guidance, and output schemas are not documented. Error handling returns generic text responses without actionable recovery steps. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Parameters lack format constraints and validation rules in descriptions.

• Document output schemas for all tools. Specify field names, types, and whether results are paginated. Example: 'Returns {catalogs: [{name: string, description: string}], total: number}'.
• Enhance error responses with recovery guidance. Categorize errors and suggest next steps: 'Catalog not found. Call getCatalogs() to see available catalogs.' or 'Query timeout (>30s). Simplify the query or add a LIMIT clause.'
• Expand tool descriptions to 100-200 chars. Add dependency hints for discovery tools: 'Call getCatalogs() first to get available connection names, then use them in other tools.'
• Add tool annotations: mark execData with destructiveHint=true; mark all read-only tools with readOnlyHint=true; mark idempotent tools with idempotentHint=true.
• Add parameter constraints in descriptions. E.g., 'query: SQL statement (max 10,000 chars, supports SELECT/INSERT/UPDATE/DELETE, parameters prefixed with @)' and 'defaultSchema: optional schema name (alphanumeric, max 128 chars)'.

Inferred effective spec: <=2025-11-25.

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