The EVE Online OSINT server demonstrates basic tool structure with names following verb_noun conventions and input schemas present. However, there are critical gaps in parameter documentation, output schema clarity, and error handling guidance. Tool descriptions are present but relatively generic (average ~80 chars, below the 194-char baseline for A-grade tools). No parameter descriptions visible in the schemas, all 9 tools list parameters with types but lack the explanatory text that helps LLMs understand constraints and purpose. Output schemas are not explicitly documented in the code, forcing LLMs to infer response structure. Error handling provides raw HTTP status codes without actionable recovery guidance.

• Add parameter descriptions to all 9 tools. For each numeric ID parameter (alliance_id, character_id, corporation_id), add: 'A positive integer identifying the EVE Online [entity]. Obtain via resolve_entity_name_to_id() or ESI lookups.' For string parameters (name in resolve_entity_name_to_id), add: 'The character, corporation, or alliance name to resolve (case-insensitive). Supports partial matches.'
• Document output schemas for each tool. Create a schema block in the tool registration stating: 'Returns: {field_name: type, ...}' with a note on chaining IDs. Example for get_character_info: 'Returns: {character_id: number, name: string, corporation_id: number, alliance_id?: number, security_status?: number, ...}. Use character_id and corporation_id for follow-up get_character_killmails() and get_corporation_info() calls.'
• Wrap HTTP errors in actionable recovery guidance. Modify error handling to detect status codes (404, 429, 500) and return: 'Alliance 9999999 not found. Try resolve_entity_name_to_id(name="[alliance_name]") first to find the correct ID.' or 'Rate limited (429). Retrying in 5 seconds.' This guides LLMs on next steps.
• Enhance tool descriptions to 50-200 characters with WHEN guidance. Example: 'Get basic alliance details including founder, executor, and creation date. Call this after resolve_entity_name_to_id() if you only have the alliance name. Returns minimal info; use get_alliance_corporations() to list member corporations.'
• Add pagination support to get_alliance_corporations() and get_corporation_members(). Introduce optional parameters: limit (1-100, default 50) and offset (default 0). Document max results: 'Returns up to 50 corporations per call. Use offset to fetch additional batches.' Update descriptions accordingly.