Server Quality Checklist

Tool Scores

• germane_binoculars--zillow-leads-property-dataA
  4.2/5.0
  Behavior4/5

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

  With no annotations, the description carries the full burden and does a good job: it discloses asynchronous behavior ('Live-collect orders take minutes'), the status/nextStep response pattern, and how to retrieve data via get-actor-run and get-dataset-items. It stops short of covering costs, rate limits, or error states, so a 4 rather than 5 is appropriate.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences, front-loaded with the core purpose and followed by the most important behavioral note. Every sentence earns its place with no redundancy or filler.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  This is a complex 11-parameter tool with no output schema, but the rich parameter schema compensates. The description covers purpose, return contents, and the critical async polling workflow. It omits the three mode distinctions (catalog/custom_search/recent_activity) at the overview level, but those are thoroughly documented in the schema, so the overall package is reasonably complete.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so baseline is 3. The description adds a small behavioral context about live-collect orders that relates to waitSecs/timeoutSecs, but it does not add meaningful parameter-level meaning beyond what the schema already provides. Thus it stays at the baseline.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states a specific action: 'Calls the Actor ... and retrieves its output results.' It names the exact tool resource and enumerates the output contents (agent/broker contact info, price/tax history, foreclosure flags, schools). Since there are no sibling tools to differentiate from, this fully satisfies purpose clarity.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description gives clear context for when this tool is appropriate: obtaining enriched Zillow listings. It also provides practical usage guidance about live-collect orders taking minutes and how to poll/fetch results. However, it doesn't explicitly state exclusions or alternatives (though none are provided), so it falls just short of a 5.

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