Voyager has 25 tools with consistent naming (verb_noun pattern) and basic descriptions. However, most descriptions are extremely brief (10-30 chars), falling well below the 50-200 char LLM-optimized baseline. Parameter descriptions exist but are minimal. No output schemas are documented. Error handling is absent, tools return raw results with no recovery guidance. The server lacks tool annotations (readOnlyHint, destructiveHint), permission gates on destructive operations, and audit logging. While tool definitions are visible and schemas are present in code, the quality is mediocre across the board.

• Expand all tool descriptions to 80-150 chars. Include WHAT the tool does, WHEN to use it, and what it returns. Example: 'Create a new project to organize tasks and documents. Returns project_id for use in subsequent calls. Use this before creating tasks or documents.'
• Document output schemas for all tools. Specify return type (object/array), required fields, and field types. Example for create_project: 'Returns {project_id: string, title: string, created_at: ISO8601, ...}'
• Add error handling with recovery guidance. Return structured errors like {error: 'not_found', message: 'Project not found', suggestion: 'Call list_projects() to see available projects'}
• Implement confirmation pattern for destructive tools. Add optional 'confirm' parameter or separate 'confirm_delete_project' tool. Require explicit confirmation before irreversible deletion.
• Add tool annotations via FastMCP. Mark read-only tools with readOnlyHint=true, destructive tools with destructiveHint=true, and idempotent tools with idempotentHint=true for client safety inference.