Detailed healthcare data for one ZIP code. Use when get_zip_profile's healthcare section isn't sufficient depth. Includes hospital count and ratings, nursing homes, beds per capita, primary care and mental health shortage area designations, pharmacy count, and urgent care count.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It describes the returned data comprehensively, but does not explicitly state it is a read-only operation or mention any auth or rate limit constraints. However, the 'get' verb implies non-destructive behavior, and data listing is sufficient for transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise (about 3 lines), front-loaded with purpose, and every sentence provides value. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has only one parameter and no output schema, the description fully covers the expected return data (hospitals, nursing homes, beds, shortage areas, pharmacies, urgent cares). It is complete for a data retrieval tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% (no description in input schema). The description only says 'one ZIP code' but does not explain the format, validation, or constraints of the zip parameter. This does not add adequate meaning beyond the field name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides 'detailed healthcare data for one ZIP code' and lists specific data points (hospital count, ratings, nursing homes, etc.), distinguishing it from sibling get_zip_profile's healthcare section.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use when get_zip_profile's healthcare section isn't sufficient depth', providing clear when-to-use guidance and naming the alternative sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool has a clearly distinct purpose. Domain-specific profiles (e.g., get_air_quality_profile) are explicitly for deeper dives after get_zip_profile, while search, reverse geocode, research, and methodology tools each serve unique roles with no overlap.
All tools follow a consistent verb_noun pattern: get_<domain>_profile, search_zips, reverse_geocode, compare_zips, get_research, get_methodology, etc. The naming is predictable and clear, with no mixing of conventions.
22 tools is slightly above the typical well-scoped range, but each tool addresses a specific need (12 domain profiles, search, geocoding, articles, methodology, ping). The count is appropriate for the breadth of data offered.
The tool surface covers the full workflow: discover (search_zips, get_search_fields), retrieve (get_zip_profile, domain profiles), compare (compare_zips), and ancillary (reverse_geocode, get_research, get_methodology). There are no dead ends or obvious gaps.
