search_neighborhoods

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Describes the process: geocode city, find state, return counties and places with data. No annotations exist, so the description carries the burden; it does so adequately for a read-only search tool.

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?

Front-loaded with the main purpose and includes args documentation. Slightly wordy with the 'Args:' section but remains clear and efficient overall.

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 output schema exists, the description adequately covers behavioral details and parameter meaning, making it complete for a search tool with one parameter.

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?

With 0% schema description coverage, the description provides crucial format guidance ('City name with state (e.g., Austin, Texas)') that the schema lacks, fully compensating for the gap.

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 searches for neighborhoods/areas in a city with housing stats, distinguishing it from sibling tools like 'get_housing_stats' or 'get_area_demographics' which focus on specific areas.

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?

It specifies the input format (city with state) and implies usage for discovering neighborhoods, but does not explicitly state when to use this vs. alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.