zillow_property: GET /

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

Discloses optional email extraction and cost increase. Without annotations, describes returned data but not side effects, errors, or rate limits. Adequate but not comprehensive.

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?

Title and three sentences: action, data list, use cases. No wasted words, front-loaded with key 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?

Lists extensive data fields (price history, Zestimate, etc.) despite no output schema. Sufficient for agent to decide to call. Lacks error or pagination details but acceptable.

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 covers both parameters with descriptions. Description adds context for email extraction ('plus email when enabled') but does not significantly enhance beyond schema. Schema coverage is 100%.

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?

Clearly states the action (Get Zillow Property Details) and resource (property by URL/zpid). Lists returned data and use cases, distinguishing it from sibling listing tools.

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?

Explicitly lists use cases (valuation models, CMA generation, etc.), implying when to use. Does not explicitly mention alternatives or when not to use, but siblings like getRealEstateListings provide implicit contrast.

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