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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the operational safety. The description adds value by listing the return fields (prices, addresses, beds, baths, sqft), providing the agent with expectations about the output format.

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 concise with a brief introductory sentence followed by a structured list of parameters. Every sentence adds value, and the format is easy to parse.

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 the low complexity (4 parameters, no output schema) and annotations covering safety, the description is fairly complete. It covers the purpose, parameters, and return fields. It could mention pagination or result limits, but it is adequate for a search 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?

With 0% schema description coverage, the description fully compensates by providing clear usage examples for location, explaining the meaning of 0 for min_price and max_price, and enumerating valid values for property_type ('house', 'condo', 'townhouse', or '' for all).

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 searches Redfin for property listings by location and filters, specifying the return fields (prices, addresses, beds, baths, sqft). This distinguishes it from sibling tools like get_property_details (which targets a specific property) and other search tools.

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 clearly indicates when to use this tool: when searching for property listings on Redfin. It does not explicitly state when not to use or suggest alternatives, but the context is straightforward given the sibling list.

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