search_properties

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

With no annotations provided, the description carries the full burden. It states that the ads are contact-the-seller, implying no direct online purchase, which is useful behavioral context. However, it does not mention other behaviors like pagination, result format, or any side effects, leaving room for 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 two concise sentences, front-loaded with the core action and scope, and efficiently communicates key distinctions and filter categories without unnecessary detail.

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 tool's complexity (12 parameters, no output schema), the description provides essential context: what is searched, the domain, and the interaction model (contact-seller). It does not detail pagination or result structure, but that is not strictly required without an output schema. The description is adequate for an agent to select and invoke the tool 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?

The schema already provides 100% description coverage for all 12 parameters, so the baseline is 3. The description text adds a high-level summary of filter types (bedrooms, bathrooms, area, sale/rent) but does not add new meaning beyond the schema. It reinforces but does not enhance parameter understanding.

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 the tool searches classified property ads, specifies property types (houses, apartments, land) and transaction types (sale/rent). It also distinguishes this from product search by noting it is not add-to-cart, which is effective given sibling tools like search_products and search_vehicles.

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 implies when to use it (when searching for property listings) and hints at differentiating it from product search via the 'not add-to-cart' note. It does not explicitly name alternatives, but the context of sibling tools and the property-specific language provides clear guidance.

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