Single tool with reasonable schema and basic description. Naming follows verb_noun convention (get_forecast). Schema is properly formatted JSON with required fields. However, description is minimal (11 words) and lacks context about use cases, prerequisites, or output structure. Parameter descriptions are entirely absent, latitude and longitude are self-explanatory numerically but lack constraints (range, precision). No documented output schema or error handling guidance. Example from code: Tool 'get_forecast' has InputSchema as JSON with latitude/longitude as required properties (good), but no description of what happens on API failure, what forecast format is returned, or when to call this tool. The tool definition is explicitly visible in examples/weather/tools.go, so no inference penalty applies.

• Expand tool description to 50-200 characters explaining: WHAT it does (returns weather forecast), WHEN to use it (when user asks about weather at a location), WHAT data it returns (periods with detailed forecasts). Example: 'Get the National Weather Service forecast for a geographic location (lat/lon). Returns detailed forecast text for upcoming periods. Requires valid coordinates between -90/90 latitude and -180/180 longitude.'
• Add description to latitude parameter: 'Latitude in decimal degrees. Range: -90 (South Pole) to +90 (North Pole). Example: 40.7128 for New York City.'
• Add description to longitude parameter: 'Longitude in decimal degrees. Range: -180 (International Date Line west) to +180 (International Date Line east). Example: -74.0060 for New York City.'
• Document output schema in tool description or via a separate schema field. Example: 'Returns an array of forecast periods, each with a detailed_forecast text field describing conditions, temperature, and precipitation probability.'
• Add error guidance to description: 'If the coordinates do not match any forecast grid, the API will return an error. Verify your latitude is between -90 and 90, and longitude between -180 and 180. For US locations, coordinates should align with land; ocean or international coordinates may not be supported.'
• Add min/max constraints to the JSON Schema for latitude and longitude (minValue: -90, maxValue: 90 for latitude; minValue: -180, maxValue: 180 for longitude) so clients can validate before calling.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry