zillow_search

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

No annotations are provided, so the description carries the burden. It mentions that results are 'normalized' and 'public listing search results,' but does not disclose much about side effects, idempotency, or safety. Since it's a search, it's likely read-only, but no explicit statement.

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?

Two sentences, no wasted words, front-loaded with the action verb 'Search.' Every sentence adds necessary information.

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?

No output schema exists, and the description only gives a high-level description of return type ('normalized...'). It does not explain the page or status parameters' role in the output. For a tool with 9 parameters, the description is somewhat incomplete for a comprehensive understanding.

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 coverage is 100% with each parameter having its own description. The tool description adds value by explaining the map bounds vs region_id fallback relationship, but does not add per-parameter detail beyond what schema provides. Baseline score 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 clearly states 'Search Zillow listings' and 'Returns normalized Zillow public listing search results,' which is a specific verb+resource description. It distinguishes from siblings like zillow_property (single property) and zillow_autocomplete (autocomplete).

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 provides explicit guidance: 'Callers must pass complete map bounds from autocomplete when available, or a region id fallback.' This tells the AI agent how to invoke the tool correctly with the right parameters, though it does not explicitly compare to alternative tools.

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