Server has 8 tools with consistent naming (verb_noun pattern) and reasonable descriptions (avg ~150 chars). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are completely undocumented, LLMs cannot predict response structure for chaining. Parameter descriptions lack format constraints (e.g., ISO 8601 format stated in description but not enforced). Error handling is minimal; no recovery guidance. Missing tool annotations (readOnlyHint/destructiveHint). samsara_update_route has incomplete schema (missing 'stops' parameter definition visible in description). No pagination guidance for list tools despite mentioning cursor support.

• Document output schemas for all 8 tools. Include field names, types, and descriptions. Example: samsara_list_vehicles should document 'vehicles' array with vehicle object schema (id, name, vin, make, model, externalIds), 'pagination' object (after, hasMore), and 'total' count.
• Add 'stops' parameter to samsara_update_route input schema with full object definition matching samsara_create_route. Document that stop IDs are auto-preserved when updating.
• Add tool annotations: mark samsara_create_route and samsara_update_route with destructiveHint=true; mark all read tools with readOnlyHint=true; mark create/update with idempotentHint=true if they support idempotency keys.
• Add JSON Schema constraints: 'limit' with minimum=1, maximum=512; 'startTime'/'endTime' with format='date-time'; 'vehicleIds' with minItems=1 where required. Move constraints from description text into schema.
• Enhance error messages with recovery guidance. Example: 'Vehicle not found (404). Try samsara_list_vehicles() to find valid IDs.' Categorize errors as retryable (429, 5xx) vs user-fixable (400, 404) vs fatal.