Server has 4 tools with basic schemas and descriptions. Naming follows verb_noun convention (list_agents, launch_serverless_db, delete_db, ask_agent). Descriptions are present but brief (10-50 chars). Input schemas are visible with type definitions for all parameters. However, output schemas are not documented, parameter descriptions lack detail about constraints/formats, and error handling guidance is absent. No enum constraints despite tools accepting specific values (region, provider). Missing documentation of what each tool returns and when to use it vs alternatives.

• Document output schemas in tool descriptions. Example: 'Returns a list of AgentInfo objects with fields: id (string), name (string), type (string), status (string), datasource_id (optional string).'
• Add enum constraints to region and provider parameters. Example: 'region: one of [eastus, westus, northeurope, southeastasia] (default: eastus)'
• Expand parameter descriptions with format/constraint details. Example for service_id: 'The unique identifier of the database service (UUID format, e.g. 550e8400-e29b-41d4-a716-446655440000)'
• Add error handling guidance to destructive tools. Example: 'If deletion fails with 'service_in_use', wait 30 seconds and retry. If it fails with 'not_found', the service was already deleted.'
• Implement a confirm_delete_db tool or add a 'confirm' parameter to delete_db to prevent accidental resource destruction by agents.

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

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