Two tools with basic schemas and minimal descriptions. getUserInfo and updateUserEmail both have Zod schemas (userId: string.min(1), newEmail: string.email()) visible in tools.js, but descriptions are extremely short (10-20 chars) and lack context for LLM selection. No output schema documented. No error recovery guidance. No parameter descriptions beyond type constraints. Naming is acceptable (verb_noun pattern) but descriptions fall well below the 50-200 char baseline for A+ tools. Error handling throws generic 'User not found' without recovery hints.

• Expand tool descriptions to 50-150 chars. Example: 'Fetch user info by ID. Returns user name, email, and ID. Call this to retrieve details before updating or sending messages.'
• Add parameter descriptions in the Zod schema or tool registration. Example: userId should be 'The unique user identifier (string, 1+ chars)'. newEmail should be 'Valid email address for the user account'.
• Document output schema explicitly. Example: 'Returns { user: { id: string, name: string, email: string } }' so LLMs know what fields to expect.
• Enhance error messages with recovery hints. Instead of 'User not found', return 'User not found. Available user IDs: 123, 456. Try one of these or call list_users() to see all users.'
• Mark updateUserEmail as a write/destructive operation in the description: 'Update a user's email address (modifies user record). Returns updated user object.'