redfin_property: GET /

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

No annotations are provided, so the description must cover behavioral traits. It states it fetches the full property page by URL, implying a read operation, but does not disclose whether it makes external HTTP requests, rate limits, or authentication requirements. The description is adequate but could add context like 'retrieves live data from Redfin' to aid agent decision-making.

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?

The description is two paragraphs: a brief purpose sentence followed by a detailed list of returned fields and use cases. It is efficient and front-loaded with the core purpose. The list of data points could be condensed, but overall it earns its space without being verbose.

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?

Given one parameter, no output schema, and no annotations, the description covers the tool's full capabilities: what it returns (detailed list) and when to use it (specific use cases). It lacks return format details but is sufficient for an agent to select the tool for property detail retrieval.

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% with one parameter 'url' described as 'The URL of the property on Redfin. Must be a valid Redfin property URL.' The description repeats 'by URL' but adds no additional semantic meaning beyond the schema. Baseline is 3, and no extra value is added.

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 specifies the verb 'Fetches' and the resource 'full Redfin property page by URL'. It lists extensive data fields, making the tool's purpose unambiguous. The sibling tool 'hasdata_redfin_listing_getRealEstateListings' likely focuses on listing search, while this tool retrieves details for a specific property, providing clear differentiation.

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 explicitly lists use cases: CMA reports, investor due-diligence, valuation models, listing enrichment, and buyer-assistant agents. It does not explicitly state when not to use it, but the use cases strongly imply it is for detailed property analysis per URL. An explicit alternative mention (e.g., 'Use hasdata_redfin_listing_getRealEstateListings for searching multiple properties') would improve clarity.

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