Single tool with minimal definition quality. shelter_locator has a basic description (56 chars) and input schema with two parameters, both typed and described. However, the description lacks actionable context (WHEN to use, WHAT it returns, any prerequisites). No output schema is documented. Parameter descriptions are minimal (location: 47 chars, radius: 32 chars). No error handling guidance, no pagination support despite potentially returning lists, and no indication of result limits. The tool name 'shelter_locator' is acceptable but generic; 'search_shelters' or 'find_dog_shelters' would be more action-oriented. Overall, this is a bare-minimum implementation typical of early-stage tools.

• Add a detailed output schema documenting the structure of returned shelter objects (e.g., name, address, phone, hours, distance). Include field types and descriptions.
• Expand tool description to 100 - 200 chars: 'Searches for dog shelters near a specified location within a given radius. Returns a list of shelters with contact info and distance. Use this to help users find nearby adoption resources.'
• Add pagination support: include limit (default 20, max 100) and offset/cursor parameters. Document max results in the description.
• Implement structured error responses: 'Location not found. Try a city name (e.g., San Francisco) or zip code.' or 'No shelters found within 5 miles of [location]. Try increasing the radius.'
• Replace example values in parameter descriptions with formal constraints. E.g., for radius: 'Search radius in miles (1 - 100, default 10)' instead of relying on the example.