Single tool with minimal definition quality. Tool name 'get_briefcase_status' follows verb_noun convention (+), but description is only 24 characters in Vietnamese, below the 50-200 char LLM-optimized baseline. Input schema is present and properly typed (briefcase_id: string), but lacks parameter description entirely. No output schema documented. Error handling is generic ('Lỗi khi gọi công cụ') with no recovery guidance. Tool makes external API calls but exposes no rate limiting, timeout, or retry logic to the LLM. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite being a read-only operation.

• Expand tool description to 80-150 characters in English: 'Retrieve the current status of a Vietnamese government service briefcase (dossier) by ID. Returns applicant name, service type, current status, and key dates. Call this to track application progress.'
• Add parameter description for briefcase_id: 'The briefcase/dossier code (e.g., "DVC-2024-001234"). Obtain from the application confirmation or search results.'
• Document output schema explicitly in code comments or a separate schema definition. Include field types and meanings: code (string), application_user_full_name (string|null), type (string|null), current_status (string|null), etc.
• Replace generic error handling with specific, actionable messages. E.g., 'Briefcase not found. Verify the briefcase_id is correct. Call search_briefcases() to find valid IDs.' or 'API timeout after 30s. Retry in 5 seconds.'
• Add tool annotation for read-only hint in server capabilities to signal to LLMs that this tool is safe to call without confirmation.