Find property locations

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

With no annotations provided, the description carries the full transparency burden. It explains the output contents (areas, communities, buildings with listing counts) and the search nature, but does not mention any potential errors, rate limits, or exact response structure. Still, it discloses the key behavioral trait of being a read-only lookup, which is sufficient for a simple search tool.

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, each with a clear purpose: action, output, and usage guidance. It is front-loaded with the verb and resource, and there is no redundant or irrelevant information.

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?

For a simple tool with 2 parameters and no output schema, the description covers the core functionality, output, and usage. It does not include examples or error handling, but given the low complexity, it is near-complete. The guidance about other tools adds important context for when to invoke this 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?

Schema coverage is 100% for both parameters, so the description does not need to explain their syntax. It slightly reinforces that 'query' is a place name ('by name') but otherwise adds no new meaning beyond the schema's descriptions. Baseline of 3 is appropriate.

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 for UAE property locations by name and returns matching areas, communities, and individual buildings with listing counts. It uses a specific verb (search) and distinct resource (locations), and distinguishes itself from sibling tools by noting that other property tools resolve place names automatically.

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 provides when to use the tool ('when a place name is ambiguous, or to discover what areas exist') and when not to ('Other property tools accept place names directly and resolve them for you, so you usually do not need to call this first'). This clearly differentiates it from alternatives.

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