Server Quality Checklist

Tool Scores

• hasdata_redfin_property_getPropertyDetailsA
  3.5/5.0
  Behavior2/5

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

  No annotations are provided, so the description must fully disclose behavioral traits. It only says it 'fetches' and returns data, but does not address authentication, rate limits, error behavior, or what happens with invalid URLs. This leaves the agent without operational expectations beyond the basic return field list.

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

  Conciseness4/5

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

  The description is front-loaded with the core action and includes no filler. The list of returned fields and use cases is lengthy but informative; however, it could have been trimmed slightly without losing essential guidance, so it does not earn a perfect score.

  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?

  For a simple one-parameter fetch tool with no output schema, the description covers the input, the returned data, and common use cases, which is largely sufficient for correct invocation. It falls short of complete because behavioral caveats such as rate limits and error handling are missing.

  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?

  The single parameter 'url' is fully described in the schema with 100% coverage, so the schema already provides the needed semantics. The description adds no further format, examples, or constraints beyond what the schema states, justifying the baseline score of 3.

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

  Purpose4/5

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

  The description clearly states a specific action and resource: 'Fetches the full Redfin property page by URL' and lists the many fields it returns. However, it never explicitly contrasts itself with the sibling listing tool, so the distinction is left to inference rather than stated outright.

  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 explicitly lists use cases: 'Use for CMA reports, investor due-diligence, valuation models, listing enrichment, and powering buyer-assistant agents.' This gives clear context for when the tool is appropriate, but it does not mention when not to use it or point to the sibling tool as an alternative.

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

• hasdata_redfin_listing_getRealEstateListingsA
  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 disclosure burden. It discloses pagination, the accepted keyword forms, the full set of returned listing fields, and the important behavioral exception that an address/building returns a single property card and ignores `type`. Rate-limit and error behavior are absent, but the core behavioral surface is well covered.

  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?

  Four dense, front-loaded sentences with no filler: action and pagination first, then location semantics, return fields/exception, and use cases. It is well sized for a 59-parameter tool because the schema carries the detailed filter documentation.

  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?

  Despite no output schema and no annotations, the description compensates by naming the main returned fields and explaining the single-property-card case. For a large search tool, the use cases and sibling routing make it reasonably complete, though it omits pagination-count/default behavior and error-handling expectations.

  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 the baseline is 3. The narrative mostly re-states the `keyword` semantics and the `type` exception that already exist in the schema, and it adds no new information about `page`, `sort`, or the other filter parameters. It therefore earns no bonus beyond the well-documented schema.

  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 opens with a specific, verb-driven statement: 'Searches Redfin for-sale, for-rent, or sold listings with pagination,' and enumerates the location forms and return fields. This makes the listing-search scope unmistakable and differentiates it from the single-property sibling endpoint.

  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?

  It gives concrete use cases ('real-estate market research, lead generation for agents, price/DOM trend analysis') and points to the 'Redfin Property endpoint' for deep-dive details, effectively routing an agent to the sibling after this search step. It does not phrase this as a hard when-not-to-use rule, but the guidance is unambiguous enough.

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