Get Redfin market report for a region

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so 'Read-only; safe to call repeatedly' largely restates them. What adds real value is the disclosure of the autocomplete resolution behavior, the neighborhood-empty-data edge case, and the per-metric return shape.

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 what the report contains, then input modes, then return shape, then safety. Dense but organized; a couple of long compound sentences carry several ideas but nothing is wasted.

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 correctly carries the return-value burden by specifying the per-metric `{ label, value, unit, yoy_change_fraction, ... }` structure. Combined with the input-mode guidance and edge-case warning, an agent has enough to call it correctly.

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% (baseline 3), but the description adds genuine meaning: the location-vs-region_id/region_type choice, the autocomplete resolution path, the neighborhood caveat, and the property_type default. This goes beyond the terse schema descriptions.

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?

States a specific verb+resource ('market report for a Redfin region') and enumerates the exact metrics returned (median list/sold prices, $/sqft, sale-to-list ratio, homes for sale/sold) with yoy/mom framing. This clearly sets it apart from siblings like redfin_get_price_history or redfin_search_properties.

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?

Gives explicit invocation guidance: provide either `location` (free-text via autocomplete) or `region_id`+`region_type`, and warns that neighborhoods typically return empty data. However, it never names alternative sibling tools or when NOT to use this one, so it stops short of full routing guidance.

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