Detailed school data for one ZIP code. Use when get_zip_profile's education section isn't sufficient depth. Includes school counts, student-teacher ratios, graduation rates, per-pupil spending, Title I percentage, and budget breakdown (instruction vs. admin vs. capital). May reflect data from the nearest ZIP if no schools are in this ZIP.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose all behavioral traits. It notes that data may come from the nearest ZIP if no schools exist in the given ZIP, which adds useful transparency. However, it does not mention read-only nature, response format, or any authentication/rate limit implications.
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?
Three concise sentences: first states purpose, second provides usage guidance, third lists data fields and a caveat. Information is front-loaded and every sentence earns its place with no 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?
Given the simple input (single param) and no output schema, the description covers main purpose, usage guidance, and key data fields. It lacks full details of all possible return fields but includes enough for most use cases.
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% (only param 'zip' has no description). The description says 'for one ZIP code' but does not specify format (e.g., 5-digit string) or constraints, adding minimal value beyond the schema.
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 retrieves detailed school data for one ZIP code, lists specific data points (school counts, ratios, rates, spending, etc.), and distinguishes it from sibling tool get_zip_profile by specifying when to use this tool for deeper education data.
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 directs to use this tool when get_zip_profile's education section is insufficient, providing a clear alternative. However, it does not explicitly state when not to use it or outline prerequisites.
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.
