Get Redfin property details

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

Annotations already declare readOnly/openWorld/idempotent, and the description reinforces this with 'Read-only; safe to call repeatedly' without contradicting them. It goes well beyond annotations by disclosing non-obvious behaviors: lot_size is null (never 0) for condos, primary_photo_url is dropped on the default compact view, the marketing description is omitted by default, and the internal resolution chain (initialInfo endpoint, /home/<id> redirect) is laid out. No contradiction.

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?

Front-loaded with the core purpose and organized in a logical progression: purpose, input modes, return fields, edge cases, view behavior, opt-in flags, safety. It is dense and every sentence carries information, but at roughly 200 words it tests the upper bound of conciseness, and the closing 'Read-only; safe to call repeatedly' partially duplicates what the annotations already state.

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?

With no output schema, the description must document return values itself — and it does, listing core fields plus derived fields (lot_size_acres, price_drop_*, hoa_monthly_usd, last_sold_*, tax_annual, extracted_features). It also covers edge cases (null lot size, dropped photo URL, omitted description), the include_* opt-ins, and sibling alternatives, leaving almost nothing for an agent to guess. The only omission is error behavior for invalid inputs, which is minor for a read-only tool.

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% and the schema's own per-parameter descriptions are already rich (e.g., the view enum and property_id resolution notes), so the baseline is 3. The description adds genuine value on top by explaining the cross-parameter resolution modes — which combination is fastest and which endpoint each hits — and by tying the include_* flags to specific response fields and sibling round trips. This is above baseline but not a 5 because per-parameter semantics are largely carried by the 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?

Opens with a specific verb+resource statement — 'Fetch a property's full Redfin record' — and the body distinguishes this tool from siblings by naming redfin_get_property_photos for galleries and redfin_get_price_history for price-history follow-ups. The three input modes (url, property_id alone, property_id+listing_id) further pin down exactly what this tool does and how it resolves records.

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?

Explicitly enumerates when to use each of the three input modes and labels the trade-off: 'property_id + listing_id — fastest, skips resolution.' It names alternatives with their conditions — 'use redfin_get_property_photos for the whole gallery' and 'Saves a follow-up redfin_get_price_history round trip — use this when a workflow needs both' — giving an agent clear decision criteria.

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