Detailed Census / demographics data for one ZIP code. Use when get_zip_profile's demographics section isn't sufficient depth. Includes population, housing, income distribution, education attainment, economic indicators, internet access, and public assistance rates.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the full burden of behavioral disclosure. It implies a read-only operation through the verb 'get' and lists data contents, but does not explicitly state non-destructiveness, auth requirements, or error handling. Given the tool's simplicity, this is adequate but slightly lacking explicit safety statements.
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 two sentences long, with the first sentence stating the core purpose and the second providing usage guidance. Every word is necessary and front-loaded for quick comprehension.
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?
For a simple tool with one parameter and no output schema, the description covers purpose, usage guidance, and data categories (population, housing, etc.). However, it does not mention error handling (e.g., invalid ZIP) or the return structure, which would be helpful for full completeness.
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?
The input schema has one parameter 'zip' with 0% description coverage; the description mentions 'ZIP code' but does not specify format (e.g., 5-digit), constraints, or examples. While the meaning is clear, additional details would improve parameter understanding.
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 Census / demographics data for one ZIP code', specifying the resource (Census/demographics) and scope (one ZIP code). It also distinguishes from sibling tool get_zip_profile by noting it offers greater depth, effectively differentiating its purpose.
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 advises to 'Use when get_zip_profile's demographics section isn't sufficient depth', providing direct guidance on when to prefer this tool over a specific alternative. This is clear and actionable.
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.
