Scored across 2 tools
The two tools have distinct jobs: one searches for listings and returns listing-level records, while the other fetches the full property page for a URL or zpid. The search tool also explicitly identifies itself as the entry point for the property endpoint, so an agent can assign each task easily.
Both names follow the same hasdata_zillow_entity_getThing pattern, so the set is predictable and readable. The minor inconsistency is that the verb portion is verbose and slightly redundant in different ways: getRealEstateListings versus getPropertyDetails, which makes them consistent but not perfectly parallel.
Two tools is at the borderline: the pair works well together as a search-then-details workflow, but the server is thin for a general-purpose Zillow data source. A property lookup by address or an agent lookup tool would make the count feel more complete.
The listing search plus property details covers the core real-estate data workflow: find properties, collect URLs, then fetch the full property record. The main gap is that agents cannot directly look up a property by address without first performing a keyword search, but that is a workaround through the existing search tool.