Two tools with minimal documentation. get_time has a basic description but no input schema (empty object). search_web has a proper schema with typed parameters and descriptions, but the tool description is generic and lacks context on when/why to use it. Neither tool has error handling guidance. Naming is acceptable (verb_noun pattern), but descriptions fall short of production standards (10-1024 char range; these are 34 and 95 chars respectively). No output schema documentation. No parameter validation or constraint hints.

• Add formal input schema to get_time (even if empty, document it as 'no parameters required').
• Document output schemas for both tools: get_time returns {type: 'string', description: 'ISO 8601 UTC timestamp'}, search_web returns {type: 'object', properties: {query, results: [{title, href, body}]}}.
• Expand search_web description to 150-200 chars: 'Performs a web search using DuckDuckGo. Returns up to max_results with title, URL, and snippet. Use when the user asks for current information, recent news, or external data. Returns empty results if no matches found.'
• Add error handling guidance: 'If search fails due to network error, retry once. If no results found, suggest rephrasing the query.'
• Add constraint to max_results parameter: 'Maximum number of results to return (1-50, default 5). Higher values may timeout.'
• Consider adding tool annotations (readOnlyHint: true) to both tools since they do not modify state.