Two tools with minimal descriptions and incomplete schemas. get_db_data has empty input schema ({}), violating the requirement that all tools have documented parameters. write_data has proper Zod schema with type constraints but lacks parameter descriptions. Both tool descriptions are under 50 chars and lack context on when/why to use them. No output schemas documented. No error handling guidance. No composition hints. Naming is acceptable (verb_noun pattern) but descriptions fail to meet the 10-1024 char baseline or explain prerequisites/side effects.

• Add parameter descriptions to write_data: id='UUID identifier for the new user record', name='User display name (2-100 chars)', email='User email address (must be valid email format)'.
• Expand tool descriptions to 100-200 chars. Example for get_db_data: 'Retrieve a random sample of 3 users from the production database. Use this to explore available user records or verify database connectivity. Returns user ID, name, and email for each record.'
• Document output schemas explicitly. For get_db_data, declare: 'Returns array of user objects with fields: id (UUID), name (string), email (string)'. For write_data, declare: 'Returns {success: boolean, message: string, user_id: string}'.
• Add error handling guidance. Example: 'If database is unavailable, returns error with retry guidance. If write_data receives invalid email, returns validation error listing constraints.'
• Add tool annotations (destructiveHint) to write_data so clients know this tool modifies state and may require confirmation.