Server has 3 read-only tools with basic schemas and descriptions. Naming follows verb_noun convention (search_, get_). Descriptions are present but minimal (34 - 66 chars, well below the 194-char baseline for A-grade tools). All tools have input schemas with type definitions and parameter descriptions, meeting baseline expectations for C/D-grade servers. Parameter descriptions are brief but functional. No output schema documented in code. Missing error handling guidance, no idempotency notes, and no downstream chaining IDs returned. Schemas are valid JSON Schema but lack richness, no enum constraints, no pattern validation beyond basic min/max bounds.

• Expand tool descriptions to 80 - 150 characters. Add WHEN to use, WHAT the tool returns, and how it differs from siblings. Example: 'Search for Lottie animations by keywords, tags, and other criteria. Returns up to 20 animations per page with ID, name, tags, and preview URL. Use this when you know what animation the user wants; use get_popular_animations() to browse trending animations.'
• Document output schema for each tool. Add an outputSchema field listing response fields, types, and purposes. Example: { outputSchema: { type: 'object', properties: { count: { type: 'integer', description: 'Number of results' }, animations: { type: 'array', items: { type: 'object', properties: { id, name, tags, previewUrl } } } } } }
• Add 'required: ["query"]' to search_animations inputSchema. The query parameter is semantically required for meaningful search behavior.
• Implement error handling that returns recovery guidance. Modify callTool() to catch errors and return structured error responses: { type: 'text', text: 'Animation ID "xyz" not found. Try search_animations(query="...") to find the correct ID.' }
• Add pagination guidance to descriptions. State max results per page (20) and note that limit/page params control pagination. Clarify what 'count' field represents and when to use the next page.
• Consider adding idempotency notes to read-only tools. Include text like 'This tool is read-only and safe to call multiple times with the same inputs.' Helps LLMs understand retry behavior.
• Add examples to descriptions showing typical use patterns, e.g., 'search_animations(query="loading", page=1, limit=20) returns 20 animations matching the keyword "loading" from the first page of results.' Avoid example IDs/values; use descriptive placeholders instead.