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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that the value is a model-derived estimate (AVM) rather than an authoritative price, which is a small but real behavioral nuance; it says nothing about freshness or caching.

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?

A single short sentence with no filler, and the key identifying term (Redfin Estimate) is front-loaded. It is efficient, though borderline under-specified rather than optimally informative.

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 an output schema present the return shape need not be described, and annotations cover safety, so the core is adequate. The remaining gap is guidance on how this differs from its three redfin siblings and where property_id comes from.

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% for the single required property_id, so the schema carries the parameter burden. The description adds no format or sourcing detail (e.g., where to obtain the id), so baseline 3 is appropriate.

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 resource — the Redfin Estimate (AVM) for a property — and the AVM parenthetical disambiguates it from sibling tools like redfin_property and redfin_similar. There is no verb, but the mapping to a single well-defined artifact is unambiguous.

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?

No indication of when to use this over redfin_property, redfin_search, or redfin_region_trends, and no mention of prerequisites (e.g., obtaining a property_id first). The agent must infer usage entirely from the name.

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