search_sale_listings

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

With no annotations, the description carries the full burden of behavioral disclosure. It provides some constraints (e.g., radius max 100 and requiring lat/lng, limit range 1-500) and defaults (status Active). However, it omits essential behaviors such as whether at least one location parameter is required, how return data is structured, and authentication needs.

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 front-loaded with a clear summary sentence, followed by a structured, compact parameter list. Each line is concise and informative, though the list is necessarily long for 24 parameters. No redundant text exists.

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 24 parameters and an output schema, the description covers individual parameter semantics but misses relational constraints: it does not explain whether a location filter is mandatory, how city/state/zip interact, or how offset pagination behaves. The output schema covers return values, but the search combination semantics are unclear.

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 0%, and the 'Args' list compensates fully. Every parameter receives a meaningful description with constraints, allowed values (e.g., propertyType), and defaults (e.g., status). This provides far more than the schema's bare types and defaults.

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 begins with 'Search for homes currently for sale by location, price range, size, and other criteria', clearly stating the verb (search), resource (homes for sale), and scope. The phrase 'currently for sale' distinguishes it from the sibling tool 'search_recent_sales'.

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 lists broad search criteria but does not explicitly state when to use this tool over alternatives like 'search_recent_sales' or 'get_listing_details'. It implies usage through its filter parameters but lacks explicit guidance on when-not-to-use or alternative selection.

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