zillow_search

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

No annotations are provided, so the description carries the behavioral burden. It discloses that results are 'normalized' and 'public,' and states the required coordinate/region context, but it omits details such as pagination behavior, response size, or any error conditions.

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, front-loaded with the primary purpose, and every sentence adds information. There is no filler or repetition of schema details.

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?

With 9 parameters, no annotations, and no output schema, the description should provide a more complete mental model. It explains the bounds/region-id workflow well, but leaves the required 'location' parameter's role ambiguous and does not describe the shape of the returned listings beyond 'normalized.'

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 schema already documents all 9 parameters with 100% coverage. The description adds the concept of 'complete map bounds' and 'region id fallback,' but does not substantially expand on parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: 'Search Zillow listings' and clarifies it returns 'normalized Zillow public listing search results.' This distinguishes it from sibling tools like zillow_property and zillow_autocomplete by emphasizing the search-result output.

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 provides clear, actionable usage guidance: 'Callers must pass complete map bounds from autocomplete when available, or a region id fallback.' This tells the agent when to use which parameters and references the autocomplete sibling, though it does not explicitly state when not to use the tool.

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