Get Redfin property details

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, but the description adds valuable behavioral context: lot_size/lot_size_acres are null for condos, raw description is omitted by default to save context, and extracted_features always carries structured signals. It also explains internal resolution mechanisms. No contradictions.

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 front-loaded with the purpose, then efficiently enumerates parameter options, return fields, and nullable notes. Every sentence adds value without wasted words. It is long but appropriately detailed for a complex tool.

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 no output schema, the description adequately lists returned fields including derived ones. It explains optional includes and null behavior. However, it does not detail the structure of nested objects like extracted_features or events_normalized, leaving some ambiguity for agents needing to parse those fields.

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 description coverage is 100%, so baseline is 3. The description adds extra meaning beyond the schema: for url, it states resolution via initialInfo endpoint; for property_id, it explains the redirect; for include_description, it notes that extracted_features is the structured alternative. This adds value but not overwhelmingly beyond the already descriptive schema.

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 opens with 'Fetch a property's full Redfin record,' which is a specific verb+resource combination. It distinguishes from siblings by noting that this tool returns a comprehensive set of fields and offers optional includes for price/tax history, contrasting with tools like redfin_get_price_history which focus solely on price history.

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 provides explicit guidance on when to use each parameter combination (url, property_id alone, property_id+listing_id) and explains the resolution process and performance trade-offs. It states the tool is read-only and safe to call repeatedly. However, it lacks explicit exclusions such as 'if you only need price history, consider redfin_get_price_history instead.'

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