Server has 10 tools with consistent verb-noun naming (list_, get_, create_, update_, delete_, search_, like_, unlike_). All tools have descriptions (avg ~50 chars, baseline 194 chars) and input schemas with typed parameters. However, descriptions are significantly shorter than production baselines and lack context on WHEN to use tools or dependencies between them. Parameter descriptions are present but minimal. Output schemas are not documented. Error handling guidance is absent. No tool annotations (readOnlyHint/destructiveHint) despite clear risk stratification in metadata.

• Expand tool descriptions to 100-200 chars. Include WHEN to use (e.g., 'Use to list all gists with pagination; for filtered search, use search_gists instead'). Add prerequisites and dependencies.
• Document output schemas for all tools. Specify fields returned by list_gists (e.g., gists: [{id, title, description, visibility, created_at}], total_count, page, limit). Include chaining IDs (e.g., gist_id in responses for downstream tool calls).
• Add tool annotations: readOnlyHint=true for list_gists/get_gist/get_gist_file/search_gists/get_user; destructiveHint=true for delete_gist; idempotentHint=true for get_* tools.
• Enhance parameter descriptions with format/range constraints. For 'files' object, document expected structure: {filename: string, content: string}. For 'visibility', note default behavior if omitted.
• Add error recovery guidance in descriptions. E.g., delete_gist: 'Permanently deletes a gist. This action cannot be undone. Returns 404 if gist not found, verify gist_id with list_gists or search_gists first.'