Search property listings

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

Without annotations, the description adds key behavioral context: prices are in AED, rental prices are annual, and asking prices are higher than actual sale prices. It doesn't cover pagination or defaults, but it discloses critical return-value behavior and unit semantics.

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 three sentences with clear front-loading: first sentence states the main function, second clarifies input and units, third offers a caveat and alternative. No unnecessary words.

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?

The tool has no output schema and multiple parameters, but the description covers essential semantics (place name, AED, annual rent, asking vs sold). It could mention pagination or return fields, but the current level is sufficient for an agent to use it 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 description adds meaning beyond the schema by clarifying that location is a place name and that prices are AED (with annual rent for rentals). Since schema coverage is 71%, this extra context for price and location is valuable.

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 UAE property listings with specific filters (area, price, bedrooms, type) and distinguishes itself by noting it takes a place name rather than an ID, while also referencing get_transactions for sold prices.

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 tells when to use get_transactions instead (when actual sale prices are needed) and implies when to use this tool (for current listings). It also provides the input constraint 'not an ID', giving clear usage guidance.

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