Returns the full prose of a specific ZipExplore research article. Use this for editing, fact-checking, detailed analysis, or when get_research summaries aren't enough. Valid slugs: disappearing-towns, hazard-premium, snap-economy, wealthy-retirees. Each article includes all body sections and methodology notes exactly as published.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses that the tool returns 'all body sections and methodology notes exactly as published', indicating a read-only, non-destructive operation. No contradictions. Could add more on availability or permissions, but sufficient given simplicity.
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?
Four sentences, front-loaded with purpose. Every sentence adds value: purpose, usage context, valid slugs, content details. No wasted words or redundancy.
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 context, parameter enumeration, and what the output contains. No gaps given the tool's complexity.
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?
Only one parameter 'slug' with 0% schema coverage. The description adds meaning by listing the four valid slugs ('disappearing-towns, hazard-premium, snap-economy, wealthy-retirees'), which is critical for correct invocation.
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 it 'Returns the full prose of a specific ZipExplore research article', specifying the action (returns), resource (full prose), and scope (specific article). It distinguishes itself from the sibling tool get_research by mentioning 'when get_research summaries aren't enough'.
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?
Description provides explicit context for when to use this tool ('for editing, fact-checking, detailed analysis, or when get_research summaries aren't enough') and lists valid slugs. However, it does not explicitly state when not to use it or mention alternatives beyond get_research.
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.
