Full location profile for one ZIP code across all 12 data domains: demographics, climate, tax, crime, cost of living, voting, education, healthcare, business, air quality, disaster risk, and transit. Use this to get detail on a ZIP after search, or when the user asks about a specific ZIP. For deeper data on one domain, use the domain-specific tools.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It mentions it provides a 'full location profile' but does not discuss rate limits, authentication, data freshness, error handling for invalid ZIPs, or what happens if data is unavailable. The scope is clear, but behavioral constraints are absent.
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 concise at two sentences, with the main purpose front-loaded. Every sentence adds value, and there is no redundant or vague language. It is well-structured for quick parsing.
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?
The tool returns a complex profile across 12 domains, but no output schema is provided, and the description does not explain what each domain contains or the structure of the response. It lacks context on potential errors or empty results for invalid ZIPs. Given the complexity, more detail is needed.
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 coverage is 0%—the parameter 'zip' has no description in the input schema. The tool description does not add meaning beyond 'ZIP code,' failing to specify format, length, or accepted values. This leaves the agent without guidance on how to properly fill the parameter.
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 'Full location profile for one ZIP code across all 12 data domains' using a specific verb ('get') and resource ('ZIP profile'). It lists all 12 domains, making the purpose explicit. It also distinguishes itself from sibling tools by noting that for deeper data on a domain, domain-specific tools should be used.
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?
The description explicitly states when to use this tool: 'after search, or when the user asks about a specific ZIP.' It also provides an alternative: 'For deeper data on one domain, use the domain-specific tools.' This guides the agent on when to select this tool versus its siblings.
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.
