The GEO MCP server provides 11 tools with mostly consistent naming (verb_noun patterns: search_*, download_*, get_*, list_*, cleanup_*) and basic descriptions. However, critical gaps significantly limit production readiness. While tool names are clear and follow verb conventions, parameter descriptions lack depth and specificity. Most critically, output schemas are completely undocumented, there is no visible schema documentation showing what fields the tools return, forcing LLMs to infer structure blindly. Parameter schemas are present but generic; many lack enums for constrained inputs (e.g., 'db_type' accepts 'gse, gsm, gpl, gds' but is declared as a free-form string, not an enum). Error handling is minimal, no recovery guidance, no actionable error messages, no indication of retryability. The destructive tool (cleanup_downloads_tool) lacks any confirmation pattern despite removing data. Descriptions are brief but adequate (60-100 chars), meeting the 10 - 1024 char baseline but below the 50-200 char sweet spot for LLM optimization. Code review reveals tool definitions are explicit in mcp_server.py (visible registration), so no inference penalty applies. However, the absence of documented output schemas and weak parameter constraints are major blockers for reliable agent use.

• Document output schemas for all 11 tools. Each tool must declare the structure of its response (field names, types, required vs optional fields). Example: 'Returns a list of objects, each with fields: accession_id (string), title (string), organism (string), sample_count (integer), date_released (ISO 8601 string).'
• Convert 'db_type' and 'record_types' to enum-type parameters with explicit allowed values: db_type enum [gse, gsm, gpl, gds]; record_types array of enum items. Remove free-form string type.
• Add specific error guidance to tool descriptions. State what failures are possible, whether they are retryable, and what the next step should be. Example: 'If no results found (HTTP 204), try a broader search term. If API rate-limited (HTTP 429), retry after 60 seconds.'
• Implement a confirmation pattern for cleanup_downloads_tool. Before deleting, return a summary (count, total size, accession IDs) and require the user/agent to confirm. Or split into two tools: preview_cleanup (dry-run) and confirm_cleanup (execution).
• Enhance parameter descriptions with search syntax guidance. Example: 'term (string, required): Search term using NCBI query syntax. Supports wildcards (*), boolean operators (AND, OR, NOT), and field tags (e.g., "cancer[DISEASE]" to search disease field). Max 256 characters.'
• Add pagination support to list-returning tools. Include total_count and next_offset in responses; accept offset and limit parameters. Document the default limit (currently 20) and maximum allowed.