real_time_redfin_data

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. However, it only lists operations and parameters; it doesn't mention read-only status, auth requirements, rate limits, output format, or side effects. This leaves significant behavioral ambiguity.

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 compact and front-loaded with a summary, followed by a structured list of operations. Minor redundancy exists (e.g., 'Search by Coordinates' repeated as both label and description), but overall it's efficient.

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?

This multi-operation tool has no output schema and no annotations. The description lists required params but fails to explain what each operation returns, optional parameters, or the meaning of 'property_details' (which claims no required params but presumably needs a listing identifier). This leaves users underinformed for several operations.

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?

The schema covers both operation and args generically, but the description adds operation-specific required parameters (e.g., ne_lat, ne_lng, sw_lat, sw_lng for search_coordinates), which is essential for correct invocation. This goes beyond the schema's generic 'key/value pairs' guidance.

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 states it provides 'Redfin real estate data' with specific operations for searching by location, coordinates, or polygon, plus property details and market trends. This distinguishes it from sibling tools like realtime_zillow_data or real_time_walmart_data.

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 each operation and its required parameters, giving clear context on how to invoke the tool. It doesn't explicitly compare to alternatives, but the 'Redfin' branding signals when to use this tool over other real-time data tools.

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