zillow_scraper

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

No annotations are provided, so the description must stand alone. It mentions credits cost (2 per request) and the need for a full URL, but does not disclose whether the tool is read-only, rate limits, or authentication requirements. The return object is detailed, partially compensating.

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 moderately concise but includes a lengthy sample return object inline. While front-loaded with the purpose, the return format details could be condensed. Every sentence adds value, but the structure could be tighter.

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 no output schema, the description provides a comprehensive sample return object. However, it lacks information on error handling, result limits, or pagination. For a single-parameter tool, it covers the essential usage context well.

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 only parameter 'url' has a schema description that is minimal. The tool description adds critical context: the URL must be a full Zillow search-results URL built via Zillow's own UI, with examples. This significantly enhances understanding 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 action 'extract', resource 'real estate listings from any Zillow search page', and output 'structured property data'. It distinguishes itself from sibling tools by specifying Zillow as the source, which no other sibling covers.

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 on constructing the input URL via Zillow's own UI and filters, and gives examples like for_sale, for_rent. It implies the tool is for Zillow listings but doesn't discuss when to avoid it or alternatives.

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