Server defines 6 tools with explicit schemas and descriptions. Naming follows verb_noun pattern (admin_index_*) and is consistent. Descriptions are present (avg ~120 chars) but lack actionable context for LLM selection. Schemas are well-formed with types and enums, but parameter descriptions are sparse or missing. Error handling guidance is absent, tools do not explain recovery paths. Security posture is strong (credentials via env vars, read-only mode default), but tool composition could be tighter (e.g., admin_index_build and admin_index_create are separate when they could be unified for common workflows).

• Add parameter descriptions to all tools. For each of bucket_name, scope_name, collection_name, explain: required vs optional, format (alphanumeric, max length), and when each applies (e.g., 'scope_name required only for Couchbase 7+').
• Document output schemas in tool descriptions. E.g., 'Returns array of {index_name, bucket, scope, collection, state, progress_pct}' for admin_index_list. Include field types and any IDs needed for chaining.
• Add error recovery guidance. For admin_index_create, document: 'If index already exists, call admin_index_drop first or use defer_build=true to avoid conflicts.' For admin_index_drop, note: 'Requires confirm=true to prevent accidental deletion.'
• Clarify parameter relationships in admin_index_create. Document: 'Either provide statement (preferred, full DDL) OR use helper fields (index_name, fields, etc.). Do not mix both.' Add enum or oneOf constraint if possible.
• Add numeric constraints to admin_index_settings_set. E.g., 'indexerThreads: integer, 1 - 128 (default 4)', 'memorySnapshotInterval: integer, 1 - 60000 milliseconds'. Prevent LLMs from passing invalid values.