Server has 15 tools with consistent naming (verb_noun pattern) and basic descriptions. All tools have Zod schemas with type definitions. However, many parameter descriptions are missing or trivial (null or empty), and output schemas are not documented. Error handling returns generic error messages without recovery guidance. Parameter constraints are present but descriptions lack actionable detail (e.g., 'Unix timestamp' without format clarification). No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications.

• Add non-empty descriptions to all parameters currently marked null. Use the pattern: '<field name> (<type>): <what it controls>. E.g., 'id (number): The unique Dolibarr thirdparty identifier (e.g., 42).'
• Document output schemas for all tools. E.g., 'Returns: {ok: boolean, sample: array of thirdparty objects with fields: id, name, email, phone, address, country_id, client, fournisseur}.'
• Enhance error messages with recovery guidance. E.g., instead of 'Error: Dolibarr API GET /thirdparties/999 → HTTP 404: Not found', return 'Thirdparty ID 999 not found. Verify the ID or call dolibarr_list_thirdparties() to search by name or email.'
• Add tool annotations to all tools. Use readOnlyHint: true for GET operations (dolibarr_ping, dolibarr_list_*, dolibarr_get_*), destructiveHint: true for write operations (dolibarr_create_*, dolibarr_update_*, dolibarr_add_*, dolibarr_validate_proposal).
• Clarify timestamp format in descriptions. Replace 'Unix timestamp; defaults to now if omitted' with 'Unix timestamp in seconds (e.g., 1704067200). Omit to use current time.' Also document date_start/date_end in dolibarr_add_contract_line.