Server has 10 tools with mixed quality. pearl_create and pearl_correct have detailed schemas and descriptions; most others lack visible parameter documentation in source. No tool descriptions visible for pearl_search, pearl_recent, pearl_handshake, thread_list, thread_create, pearl_stats, pearl_identity, pearl_search_similar, only tool names and file paths shown. Schema completeness varies: pearl_create has full JSON Schema with enums and required fields; others inferred but not shown. Error handling present (isError flag) but lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Output schemas not documented. Naming follows verb_noun pattern (good), but 8 of 10 tools lack visible descriptions in provided source.

• Add descriptions to all 8 undocumented tools. Each should explain WHAT it does, WHEN to use it, and what it returns. Target 50-200 characters per pattern:tool-description.
• Document input and output schemas for all tools. Use JSON Schema with type, description, and enum constraints. Include required fields and defaults.
• Add tool annotations: mark pearl_search, pearl_recent, pearl_handshake, thread_list, pearl_stats, pearl_identity, pearl_search_similar with readOnlyHint=true; mark pearl_create, thread_create, pearl_correct with destructiveHint=true.
• Enhance error responses with recovery guidance. E.g., 'Pearl not found (ID: xyz). Try pearl_search() to find pearls by content or thread.' Classify errors as retryable, user-fixable, or fatal.
• Define metadata schema in pearl_create. Replace free-form object with enum of allowed keys or a structured object with typed fields (tags: string[], context: string, etc.).