Three tools with clear verb-noun naming (search*) and reasonable descriptions (100-150 chars). All parameters have type definitions and descriptions. However, output schemas are completely undocumented, no indication of what fields are returned, what structure the results have, or how to chain results to other tools. Parameter descriptions lack format constraints, enums, or validation guidance. No error handling documentation. Missing pagination info despite tools returning lists. No indication of result limits or how to handle large result sets.

• Document output schema for each tool. Specify returned fields (e.g., character_id, name, status, species, image_url), types, and structure. Include example response.
• Add pagination support: include limit (default 20, max 100), offset/page parameters, and return total_count or next_cursor in responses. Document in tool descriptions.
• Convert informal constraints to formal enums. E.g., status parameter should declare enum: ['Alive', 'Dead', 'unknown']. Gender should be enum: ['Female', 'Male', 'Genderless', 'unknown'].
• Add error handling documentation. Specify what errors can occur (invalid status, API timeout, no results) and what the LLM should do (retry, ask user, try different search).
• Enhance parameter descriptions with format/range info. E.g., 'name: Partial or full character name (case-insensitive, 1-100 chars)' instead of just 'The name of the character to filter by'.