Two tools with basic verb-noun naming (get-weather, get-time) and minimal descriptions. Both have simple input schemas with a single 'city' parameter. Descriptions are present but generic (10-50 chars), below the 194-char baseline for production tools. No parameter descriptions provided, LLMs cannot infer what 'city' means without context. No output schemas documented. No error handling guidance. Tools are READ_ONLY but lack explicit risk annotations. Schemas are present but minimal; parameters lack descriptions, violating the 100% baseline for A+ tools.

• Add parameter descriptions: 'city: The name of the city (e.g., London, New York, Tokyo). Accepts city names in English.'
• Expand tool descriptions to 100-200 chars: 'Retrieves current weather conditions for a specified city, including temperature in Celsius and weather condition. Use this when the user asks about weather. Returns temperature and condition string.'
• Document output schema in tool description or as a structured comment: 'Returns {temperature: number (°C), condition: string (e.g., Sunny, Rainy, Cloudy)}'
• Add error handling guidance: 'If city not found, returns error with available cities. Retry with a different city name or ask user for clarification.'
• Declare tool annotations in schema: add readOnlyHint=true to indicate these are safe, non-destructive calls