zillow_property: GET /

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

No annotations provided, so description carries full burden. It mentions increased cost for agent email extraction but lacks details on rate limits, authentication, or any destructive behavior. Partial transparency.

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?

Description is a single paragraph that is fairly concise given the amount of information. It front-loads the main purpose and lists many return fields without excess verbiage.

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, but the description enumerates many return fields (address, price, Zestimate, etc.), providing a good sense of what to expect. Lacks error handling details, but it's adequate for a property details tool.

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%, but the description adds value by stating the URL fetches the full property page and that extractAgentEmails increases cost. This goes beyond schema definitions.

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 it fetches Zillow property details by URL/zpid and lists many return fields. However, it does not explicitly distinguish from sibling tools like Redfin property details, though the name makes it clear.

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 lists several use cases (valuation, CMA, underwriting, etc.), providing implied guidance. However, it does not specify when not to use this tool or compare with alternatives like Redfin.

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