Single tool 'show-weather' has a basic description and input schema, but lacks depth. Description is minimal (54 chars, below the 194-char baseline for A+ tools). Schema defines only 'city' parameter with a generic description. No output schema documented. No error handling guidance. No parameter constraints (e.g., min length enforcement). Tool is read-only but lacks explicit idempotent annotation. Overall structure is present but falls short of production quality.

• Expand tool description to 100-200 chars: explain what weather data is returned, when to call it, and what format the response uses (e.g., 'Returns current temperature, conditions, and humidity for a given city as a JSON object with fields: temperature (number), condition (string), humidity (number).').
• Add explicit output schema documenting response fields: temperature, condition, humidity, and their types. This enables LLMs to extract and chain data correctly.
• Add minLength and maxLength constraints to the 'city' parameter in the JSON Schema (e.g., minLength: 1, maxLength: 100) rather than relying on description text.
• Add error handling guidance: 'If city is not found, returns error with available cities. If weather service is unavailable, returns timeout error, retry after 30 seconds.'
• Add idempotentHint: true to the tool definition to signal that repeated calls with the same city produce the same result and are safe to retry.