GEOPulse defines 9 tools with clear action verbs and domain-specific descriptions. Most tools have proper input schemas with type definitions. However, several critical gaps reduce quality: (1) parameter descriptions are sparse or missing entirely (e.g., 'hours_back' in get_safety_events lacks guidance on valid range); (2) output schemas are completely undocumented, LLMs cannot plan downstream calls or extract fields; (3) error handling is absent from descriptions; (4) no pagination guidance for list-returning tools; (5) query_fleet_data exposes raw SQL, creating injection risk without sanitization guidance. Tool names follow verb_noun convention well (get_*, create_*, find_*). Descriptions are moderately detailed (avg ~120 chars) but lack 'when to use' context and recovery guidance.

• Document output schemas for all tools. Example: get_fleet_overview returns {vehicles: [{id, name, lat, lon, deviation_score, status}], total_count, timestamp}. This enables LLMs to extract and chain data.
• Add parameter range/format guidance: 'hours_back: integer, 1-720 (1 hour to 30 days)'; 'threshold: integer, 0-100 (deviation percentile)'; 'data_summary: JSON string, max 10KB'.
• Implement SQL injection prevention in query_fleet_data: validate table/column names against a whitelist, use parameterized queries, document allowed tables in description.
• Add pagination to list-returning tools: accept limit (1-100, default 20) and offset/cursor parameters; return total_count and next_cursor in response.
• Include error recovery guidance in descriptions: 'If driver not found, call find_anomalous_drivers() to discover available drivers' or 'Retryable on timeout; non-retryable on invalid threshold.'